Get comprehensive location context in one call: location details, present characters, and items here. Reduces multiple tool calls to one.
AI agents call get_location_context to retrieve information from DMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only operations on game state data. It aggregates information about a location (details, characters, items) without creating, modifying, deleting, or executing external operations. The semantic purpose is informational retrieval for an RPG dungeon master, with no side effects or irreversible actions.
From the tool's definition Tool description explicitly states it 'Get[s] comprehensive location context' and 'Reduces multiple tool calls to one', indicating it retrieves and queries game state without modifying it.
Documented attack patterns abuse exactly the kind of access get_location_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_location_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_location_context": {}
}
}get_location_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get comprehensive location context in one call: location details, present characters, and items here. Reduces multiple tool calls to one. It is categorised as a Read tool in the DMCP MCP Server, which means it retrieves data without modifying state.
Register the D MCP server in PolicyLayer and add a rule for get_location_context: 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 DMCP. Nothing to install.
get_location_context 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_context 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_context. 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_context is provided by the D MCP server (shawnrushefsky/dmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
204 DMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.