Reduce duration of all status effects (call at end of round). Returns expired and remaining effects.
AI agents use tick_status_durations 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 modifies game state by decrementing status effect durations and marking effects as expired. It is a reversible write operation within a game context, with low blast radius as it only affects in-game status tracking.
From the tool's definition Reduce duration of all status effects (call at end of round). Returns expired and remaining effects.
Documented attack patterns abuse exactly the kind of access tick_status_durations 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 tick_status_durations:
{
"version": "1",
"default": "deny",
"tools": {
"tick_status_durations": {
"limits": [
{
"counter": "tick_status_durations_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}tick_status_durations 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.
Reduce duration of all status effects (call at end of round). Returns expired and remaining effects. 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 tick_status_durations: 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.
tick_status_durations 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 tick_status_durations 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 tick_status_durations. 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.
tick_status_durations 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.