get_location
AI agents call get_location to retrieve information from DM20 Protocol without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix is a strong indicator of a read operation that retrieves data without modification. In the context of a D&D campaign management system, retrieving location information is a typical query operation. Without a description, confidence is reduced but the naming convention supports classification as Read. No blast radius concerns for an AI agent querying location data.
From the tool's definition Tool name 'get_location' suggests a retrieval operation. The empty description prevents definitive confirmation, but given the server's purpose (D&D campaign management) and sibling tools that are predominantly read/write/execute operations on game entities,…
Attacks that exploit this kind of access
get_location. It is categorised as a Read tool in the DM20 Protocol MCP Server, which means it retrieves data without modifying state.
Register the DM20 Protocol MCP server in PolicyLayer and add a rule for get_location: 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 DM20 Protocol. Nothing to install.
get_location 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_location 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_location. 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_location is provided by the DM20 Protocol MCP server (polloinfilzato/dm20-protocol). 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 →