Create exits/paths between two locations. Call this whenever you describe how locations connect to each other - the player should be able to navigate based on database connections.
AI agents use connect_locations to create or update resources in DMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DMCP environment.
This tool creates game world connections in the dungeon master's database. While it modifies game state, the operation is reversible (paths can be removed or reconfigured), has no destructive capability, and operates entirely within the RPG simulation context with no external side effects or real-world impact. It fits the Write category: creates or modifies data reversibly.
From the tool's definition Tool creates (establishes) exits/paths between two locations in the game state database. The description explicitly states 'Create exits/paths', which is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access connect_locations 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 connect_locations:
{
"version": "1",
"default": "deny",
"tools": {
"connect_locations": {
"limits": [
{
"counter": "connect_locations_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}connect_locations stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create exits/paths between two locations. Call this whenever you describe how locations connect to each other - the player should be able to navigate based on database connections. It is categorised as a Write tool in the DMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the D MCP server in PolicyLayer and add a rule for connect_locations: 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.
connect_locations is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the connect_locations 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 connect_locations. 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.
connect_locations 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.