schema_definitions
AI agents call schema_definitions to retrieve information from MCP Alchemy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
In the context of an MCP server designed for database exploration, 'schema_definitions' almost certainly retrieves schema metadata (table structures, column definitions, types, constraints) — a read-only operation with no side effects. The sibling tools (all_table_names, filter_table_names) are clearly read operations, and this fits the same pattern. Empty description reduces confidence.
From the tool's definition Tool name 'schema_definitions' combined with server context of database exploration tools (all_table_names, filter_table_names) strongly suggests this retrieves database schema/structure information. Description is empty, lowering confidence.
Attacks that exploit this kind of access
schema_definitions. It is categorised as a Read tool in the MCP Alchemy MCP Server, which means it retrieves data without modifying state.
Register the MCP Alchemy MCP server in PolicyLayer and add a rule for schema_definitions: 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 MCP Alchemy. Nothing to install.
schema_definitions 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 schema_definitions 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 schema_definitions. 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.
schema_definitions is provided by the MCP Alchemy MCP server (runekaagaard/mcp-alchemy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →