Get all available SecurityAgent API operations.
AI agents call get_api_guide to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves informational content (API guide/operations list) with no side effects. It is a documentation or discovery operation analogous to 'list' or 'get' commands, which fall under the Read category. The severity is low because exposing API documentation poses minimal risk—it provides operational knowledge but does not enable data modification, deletion, or financial transactions.
From the tool's definition Tool name 'get_api_guide' and description 'Get all available SecurityAgent API operations' indicate a retrieval operation that queries and returns API documentation or operational information without modifying any data.
Attacks that exploit this kind of access
Get all available SecurityAgent API operations. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey 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 Awslabs Valkey. 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 Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.