AI agents call get_user_policy to retrieve information from Awslabs Amazon Sns Sqs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming convention, this tool likely retrieves user policy details, which is a read operation with no side effects. However, confidence is reduced to 0.6 due to the empty description providing no explicit confirmation of the tool's actual behavior. If this tool were to return sensitive policy data that could reveal IAM permissions, it remains a Read category (high-sensitivity data, but no modification).
From the tool's definition Tool name 'get_user_policy' suggests retrieving/querying policy information. The description is empty, but the 'get_' prefix typically indicates a read operation that retrieves data without modification.
Documented attack patterns abuse exactly the kind of access get_user_policy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Amazon Sns Sqs, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user_policy:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_policy": {}
}
}get_user_policy 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_user_policy. It is categorised as a Read tool in the Awslabs Amazon Sns Sqs MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Amazon Sns Sqs MCP server in PolicyLayer and add a rule for get_user_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 Amazon Sns Sqs. Nothing to install.
get_user_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 get_user_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 get_user_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.
get_user_policy is provided by the Awslabs Amazon Sns Sqs MCP server (awslabs.amazon-sns-sqs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Awslabs Amazon Sns Sqs, 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 Awslabs Amazon Sns Sqs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.