High Risk →

readonly_query

readonly_query

How to control readonly_query ↓

What readonly_query does on Amazon Redshift MCP Server

AI agents invoke readonly_query to trigger actions in Amazon Redshift MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why readonly_query needs a policy

The name suggests a read-only SQL query against Redshift, which would normally be classified as Read. However, the description is empty, so we cannot confirm actual enforcement of read-only constraints. In Redshift contexts, 'query' tools can sometimes execute arbitrary SQL.

From the tool's definition Tool name is 'readonly_query' on an Amazon Redshift MCP server; description is empty and uninformative.

Documented attack patterns abuse exactly the kind of access readonly_query gives an agent:

How to control readonly_query

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Redshift MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for readonly_query:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "readonly_query": {
      "limits": [
        {
          "counter": "readonly_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

readonly_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Amazon Redshift MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about readonly_query

What does the readonly_query tool do? +

readonly_query. It is categorised as a Execute tool in the Amazon Redshift MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on readonly_query? +

Register the Amazon Redshift MCP Server MCP server in PolicyLayer and add a rule for readonly_query: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Amazon Redshift MCP Server. Nothing to install.

What risk level is readonly_query? +

readonly_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit readonly_query? +

Yes. Add a rate_limit block to the readonly_query rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block readonly_query completely? +

Set action: deny in the PolicyLayer policy for readonly_query. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides readonly_query? +

readonly_query is provided by the Amazon Redshift MCP Server MCP server (awslabs.redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Redshift MCP Server tool call.

Start from Amazon Redshift MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

805 Amazon Redshift MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.