Get the department and location ID mappings used by Viterbit. Returns both department names to IDs and location names to IDs.
AI agents call get_department_location_mappings to retrieve information from Viterbit 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 static or semi-static reference data (department and location IDs) without side effects. It is a simple lookup/query operation that does not modify data, execute code, delete records, or involve financial transactions. The low severity reflects minimal risk even if misused by an agent, as it only exposes metadata mappings.
From the tool's definition Tool name 'get_department_location_mappings' and description 'Get the department and location ID mappings' indicate a retrieval operation that returns reference data (mappings). No modification, deletion, or execution of external operations is described.
Attacks that exploit this kind of access
Get the department and location ID mappings used by Viterbit. Returns both department names to IDs and location names to IDs. It is categorised as a Read tool in the Viterbit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Viterbit MCP Server MCP server in PolicyLayer and add a rule for get_department_location_mappings: 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 Viterbit MCP Server. Nothing to install.
get_department_location_mappings 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_department_location_mappings 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_department_location_mappings. 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_department_location_mappings is provided by the Viterbit MCP Server MCP server (techkampe/mcp_viterbit). 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 →