get-resource-policy
AI agents call get-resource-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 'get-' prefix strongly suggests this tool retrieves and returns a resource policy, which is a Read operation. While the description is empty, diminishing confidence slightly, the naming convention is unambiguous.
From the tool's definition Tool name 'get-resource-policy' indicates retrieval of a resource policy document. The lack of description prevents full certainty, but the 'get-' prefix is characteristic of Read operations that retrieve data without modification.
Attacks that exploit this kind of access
get-resource-policy. 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-resource-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.
get-resource-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-resource-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-resource-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-resource-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.