PostgreSQL
Put PostgreSQL behind GateRook’s MCP Firewall. Follow the illustrated setup, scope AI queries, approve an UPDATE and inspect its Activity audit trail.
MCP Firewall integrations
Put databases, logs, APIs, cloud services and MCP servers behind GateRook’s MCP Firewall. Choose a connector, protect its credentials and control the actions available to your AI.
Explore the catalog
Built-in connectors, supported variants, log backends, and external MCP servers. Open any guide for setup, available tools, access boundaries, and examples.
19 of 19 integration guides
Put PostgreSQL behind GateRook’s MCP Firewall. Follow the illustrated setup, scope AI queries, approve an UPDATE and inspect its Activity audit trail.
Control MySQL access through GateRook’s MCP Firewall. Configure a scoped login, run read queries, approve an UPDATE and inspect each call in Activity.
Protect MariaDB access with GateRook’s MCP Firewall. Follow the Docker tutorial to scope SQL queries, approve an update and inspect the Activity record.
Control AI access to Oracle Database 19c and later. Protect credentials, scope schemas, bound read queries and review SQL changes through GateRook.
Put SQL Server behind GateRook’s MCP Firewall. Select databases and schemas, keep credentials local, and review SQL writes before execution.
Control MongoDB access through GateRook’s MCP Firewall. Follow the Docker tutorial to scope reads, approve updates and inspect the Activity audit trail.
Protect Redis access with scoped, read-only MCP tools. Follow the GateRook Docker tutorial to approve a value read and inspect its Activity record.
Control OpenSearch access with GateRook’s MCP Firewall. Keep credentials local, separate read APIs and review writes or administrative requests before execution.
Protect Elasticsearch access with GateRook. Keep credentials local, expose recognized read APIs and require review for writes and administrative requests.
Control AI access to Loki logs with GateRook. Configure tenant and source scope, keep credentials local and bound LogQL results and time ranges.
Control CloudWatch Logs access through GateRook. Restrict regions and log groups, keep AWS credentials local and bound queries and returned results.
Protect Google Cloud log access with GateRook. Choose projects or log views, use a scoped identity and bound the log data returned to your AI client.
Read selected SSH log files through GateRook’s MCP Firewall. Verify host keys, restrict file access and inspect bounded results and call history in Activity.
Put HTTP APIs behind GateRook’s MCP Firewall. Protect API keys, restrict destinations and paths, and approve requests that change data.
Inspect AWS through GateRook’s MCP Firewall. Scope accounts and regions, keep credentials local, and expose read-only resource and CloudWatch tools.
Control Google Cloud access through GateRook. Keep service account keys local, scope read-only inventory and monitoring, and enable log access deliberately.
Protect Kubernetes access with GateRook’s MCP Firewall. Restrict namespaces, enable log access deliberately and approve enabled rollout or manifest changes.
Control AI access to SSH with GateRook. Verify host keys, use predefined runbooks and review rendered commands before approving server changes.
Put stdio or Streamable HTTP MCP servers behind GateRook’s MCP Firewall. Review tools, configure secret injection, choose access modes and audit calls.
Beyond built-in connections
Apply endpoint policies and approval controls to the tools you expose.
Connect a local stdio or remote Streamable HTTP server. GateRook can discover servers through the Official MCP Registry, then lets you review the connection details and decide which tools to expose.
Registry discovery is not a security certification. Review the server and its permissions before connecting; you control its endpoint policies and approvals.
Your MCP Firewall. Your access rules.
Start with read-only access. Approve changes. Inspect the audit trail.