Query department master data. Returns all departments or filter by ID/name.
AI agents call query_departments 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 performs a straightforward data retrieval operation against master data tables. It returns existing department records filtered by optional parameters (ID or name) but does not create, modify, delete, or execute arbitrary code. The operation is a standard database query with no destructive, financial, or external side effects.
From the tool's definition Tool name 'query_departments' and description 'Query department master data. Returns all departments or filter by ID/name.' indicate a read-only operation that retrieves or lists department information with no modifications or side effects.
Attacks that exploit this kind of access
Query department master data. Returns all departments or filter by ID/name. 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 query_departments: 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.
query_departments 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 query_departments 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 query_departments. 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.
query_departments 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 →