Schedule an event to trigger at a specific in-game time
AI agents use schedule_event 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 or schedules new events within the game state, which is a reversible modification operation. It does not retrieve data (Read), execute arbitrary code or commands (Execute), permanently destroy data (Destructive), or involve financial transactions (Financial).
From the tool's definition The tool description states it 'Schedule an event to trigger at a specific in-game time', which creates or modifies game state by adding a scheduled event. The verb 'schedule' indicates a creation action that modifies the game's event system.
Documented attack patterns abuse exactly the kind of access schedule_event 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 schedule_event:
{
"version": "1",
"default": "deny",
"tools": {
"schedule_event": {
"limits": [
{
"counter": "schedule_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}schedule_event 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.
Schedule an event to trigger at a specific in-game time. 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 schedule_event: 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.
schedule_event 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 schedule_event 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 schedule_event. 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.
schedule_event 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.