Get the database schema information including table structures and column definitions.
AI agents call get_schema to retrieve information from Bakery Data MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves structural metadata about the database (table and column definitions). It has no side effects, does not execute code, and does not modify data. It is purely informational and falls squarely into the Read category. Severity is low because schema disclosure alone poses minimal risk unless combined with other tools like execute_sql, which are separately classified.
From the tool's definition Tool name 'get_schema' and description 'Get the database schema information including table structures and column definitions' indicate retrieval of metadata without modification or execution of arbitrary code.
Attacks that exploit this kind of access
Get the database schema information including table structures and column definitions. It is categorised as a Read tool in the Bakery Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bakery Data MCP Server MCP server in PolicyLayer and add a rule for get_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 Bakery Data MCP Server. Nothing to install.
get_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_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_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_schema is provided by the Bakery Data MCP Server MCP server (t2hnd/bakery_data_mcp). 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 →