Generate security-approved IAM policy for SQS ESM with scoped permissions. Uses pre-approved templates, not LLM generation.
AI agents call secure_esm_sqs_policy 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.
The tool generates/outputs an IAM policy document using pre-approved templates. It does not attach, apply, or modify any actual IAM policy — it only produces the policy text. This is effectively a read/query operation that returns a templated document. No side effects are described.
From the tool's definition Generate security-approved IAM policy for SQS ESM with scoped permissions. Uses pre-approved templates, not LLM generation.
Attacks that exploit this kind of access
Generate security-approved IAM policy for SQS ESM with scoped permissions. Uses pre-approved templates, not LLM generation. 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 secure_esm_sqs_policy: 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.
secure_esm_sqs_policy 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 secure_esm_sqs_policy 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 secure_esm_sqs_policy. 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.
secure_esm_sqs_policy 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.