Search Aurora DSQL documentation
AI agents call dsql_search_documentation to retrieve information from Amazon Data Processing MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries documentation content, which is a read-only operation that retrieves information without side effects. Searching documentation poses minimal risk as it cannot modify data, execute code, or trigger external operations. The low severity reflects that documentation searches are informational queries with negligible blast radius.
From the tool's definition Tool name contains 'search' and description states 'Search Aurora DSQL documentation' - clearly a documentation retrieval operation with no data modification or execution capability.
Documented attack patterns abuse exactly the kind of access dsql_search_documentation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Data Processing MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for dsql_search_documentation:
{
"version": "1",
"default": "deny",
"tools": {
"dsql_search_documentation": {}
}
} dsql_search_documentation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search Aurora DSQL documentation. It is categorised as a Read tool in the Amazon Data Processing MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon Data Processing MCP Server MCP server in PolicyLayer and add a rule for dsql_search_documentation: 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 Data Processing MCP Server. Nothing to install.
dsql_search_documentation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dsql_search_documentation 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 dsql_search_documentation. 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.
dsql_search_documentation is provided by the Amazon Data Processing MCP Server MCP server (awslabs.aws-dataprocessing-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Data Processing 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 Data Processing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.