Fetch table columns from SQL Server
AI agents call get_table_schema 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.
This tool retrieves schema metadata (column information) from a SQL Server database. It is a read-only operation that queries and returns structural information about tables without modifying, deleting, or executing arbitrary code. The blast radius is minimal as it only exposes schema structure, not sensitive data rows, and produces no side effects.
From the tool's definition Tool name 'get_table_schema' and description 'Fetch table columns from SQL Server' indicate data retrieval with no modification capability.
Attacks that exploit this kind of access
Fetch table columns from SQL Server. 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_table_schema: 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_table_schema 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_table_schema 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_table_schema. 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_table_schema 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.