gateway_resource_policy_get
AI agents call gateway_resource_policy_get 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.
Based on naming convention, 'get' operations retrieve data without side effects. However, confidence is moderate (0.7) rather than high because the description is empty, leaving some ambiguity about the tool's actual behavior. If this tool merely retrieves gateway resource policy information, it qualifies as a Read operation with low severity since policy retrieval has minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'gateway_resource_policy_get' uses the 'get' verb, which typically indicates a retrieval operation. The tool name structure suggests fetching an existing resource policy rather than modifying or deleting it.
Attacks that exploit this kind of access
gateway_resource_policy_get. 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 gateway_resource_policy_get: 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.
gateway_resource_policy_get 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 gateway_resource_policy_get 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 gateway_resource_policy_get. 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.
gateway_resource_policy_get 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.