Search the LocalStack documentation to find guides, API references, and configuration details
AI agents call localstack-docs to retrieve information from Localstack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum number of results to return. |
query | string | Yes | The search query. |
Parameters from the server's own tool schema.
This is a documentation search utility that queries and retrieves existing knowledge base content. It performs no writes, executions, deletions, or financial operations. The blast radius of misuse is minimal—an agent could only retrieve documentation that is already public/accessible, posing no security or operational risk.
From the tool's definition Tool description states 'Search the LocalStack documentation to find guides, API references, and configuration details' — the verb 'search' and the object 'documentation' indicate read-only retrieval of information with no side effects or state modifications.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search the LocalStack documentation to find guides, API references, and configuration details. It is categorised as a Read tool in the Localstack MCP Server, which means it retrieves data without modifying state.
localstack-docs accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Localstack MCP server in PolicyLayer and add a rule for localstack-docs: 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 Localstack. Nothing to install.
localstack-docs 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 localstack-docs 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 localstack-docs. 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.
localstack-docs is provided by the Localstack MCP server (@localstack/localstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →