Look up a location by name within a game. Supports exact, partial, and fuzzy matching. Returns the best match or an error if no reasonable match found.
AI agents call get_location_by_name 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 is a pure query/retrieval function that searches and returns location information within the game world. No side effects, state changes, or external operations are indicated. It is classified as Read with low severity because misuse would only retrieve information rather than cause harm or unintended consequences.
From the tool's definition Tool performs a lookup operation ('Look up a location by name') that queries existing game state and returns matching location data.
Documented attack patterns abuse exactly the kind of access get_location_by_name 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_by_name:
{
"version": "1",
"default": "deny",
"tools": {
"get_location_by_name": {}
}
}get_location_by_name 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.
Look up a location by name within a game. Supports exact, partial, and fuzzy matching. Returns the best match or an error if no reasonable match found. 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_by_name: 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_by_name 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_by_name 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_by_name. 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_by_name 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.