Create a countdown, stopwatch, or segmented clock
AI agents use create_timer 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.
The tool creates a new game object (timer/clock) within the RPG session state. This is a reversible data creation operation with limited blast radius—misuse would only affect the current game session's timing mechanics, not cause irreversible damage or affect external systems. It aligns with Write category as it modifies game state without destructive, financial, or code-execution implications.
From the tool's definition Tool name 'create_timer' and description 'Create a countdown, stopwatch, or segmented clock' indicate creation of a game-state time tracking object.
Documented attack patterns abuse exactly the kind of access create_timer 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 create_timer:
{
"version": "1",
"default": "deny",
"tools": {
"create_timer": {
"limits": [
{
"counter": "create_timer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_timer 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 a countdown, stopwatch, or segmented clock. 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 create_timer: 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.
create_timer 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 create_timer 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 create_timer. 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.
create_timer 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.