Get all available SecurityAgent API operations. Returns operation names dynamically from the service model, plus a link to full API documentation with parameter details.
AI agents call get_api_guide to retrieve information from AWS without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists API operations and documentation references. It has no side effects, does not execute operations, modify data, or trigger external actions. It is purely informational/read-only access to API metadata.
From the tool's definition Tool description states 'Get all available SecurityAgent API operations' and 'Returns operation names dynamically from the service model, plus a link to full API documentation'.
Documented attack patterns abuse exactly the kind of access get_api_guide gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS, and nothing reaches the server without passing your rules. This is the rule we recommend for get_api_guide:
{
"version": "1",
"default": "deny",
"tools": {
"get_api_guide": {}
}
} get_api_guide 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.
Get all available SecurityAgent API operations. Returns operation names dynamically from the service model, plus a link to full API documentation with parameter details. It is categorised as a Read tool in the AWS MCP Server, which means it retrieves data without modifying state.
Register the AWS MCP server in PolicyLayer and add a rule for get_api_guide: 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. Nothing to install.
get_api_guide 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 get_api_guide 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 get_api_guide. 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.
get_api_guide is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS, 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.
300 AWS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.