get_resource_schema_information
AI agents call get_resource_schema_information 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 name strongly suggests it retrieves schema information without modifying data. However, confidence is moderate due to empty description—if it were more clearly documented, confidence would be higher. No evidence of side effects, data modification, or destructive capability based on available information. Classified as Read with low severity due to limited blast radius of schema information exposure.
From the tool's definition Tool name 'get_resource_schema_information' indicates retrieval of schema metadata; no description provided but naming pattern suggests a read-only query operation typical of schema introspection.
Attacks that exploit this kind of access
get_resource_schema_information. 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_schema_information: 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_schema_information 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_schema_information 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_schema_information. 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_schema_information 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.