Run a SQL query against Microsoft SQL Server
AI agents invoke run_query to trigger actions in AWS Documentation 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.
SQL query execution is an Execute category risk because it triggers external operations (database queries) whose effects depend entirely on the arguments provided. An AI agent could be tricked into running destructive queries (DROP, DELETE, ALTER), data exfiltration queries, or resource-intensive operations.
From the tool's definition Tool name is 'run_query' with description 'Run a SQL query against Microsoft SQL Server'. The term 'run' combined with SQL query execution indicates arbitrary code execution capability against a database.
Documented attack patterns abuse exactly the kind of access run_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Documentation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_query:
{
"version": "1",
"default": "deny",
"tools": {
"run_query": {
"limits": [
{
"counter": "run_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_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.
Free to start. No card required.
Run a SQL query against Microsoft SQL Server. It is categorised as a Execute tool in the AWS Documentation MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS Documentation MCP Server MCP server in PolicyLayer and add a rule for run_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 AWS Documentation MCP Server. Nothing to install.
run_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_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.
Set action: deny in the PolicyLayer policy for run_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.
run_query is provided by the AWS Documentation MCP Server MCP server (awslabs.aws-documentation-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Documentation 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 AWS Documentation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.