AI agents invoke check to trigger actions in DMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a game mechanic (skill/ability check) which involves computation and likely modifies game state (e.g., recording results, affecting outcomes). It triggers an external operation within the RPG game engine. Severity is low as it only affects in-game state of a text-based RPG with no real-world consequences.
From the tool's definition Perform a skill or ability check
Documented attack patterns abuse exactly the kind of access check 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 check:
{
"version": "1",
"default": "deny",
"tools": {
"check": {
"limits": [
{
"counter": "check_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}check stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Perform a skill or ability check. It is categorised as a Execute tool in the DMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the D MCP server in PolicyLayer and add a rule for check: 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.
check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the check 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 check. 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.
check 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.