Configure the calendar system for a game (months, days per month, hours per day, etc.)
AI agents use set_calendar 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 configuration (calendar parameters like months, days, hours) but does not delete data, execute external code, or cause financial transactions. The effects are reversible through reconfiguration. In the context of an RPG dungeon master system, configuring game mechanics is a standard Write operation with low severity since misconfiguration affects only the game session and can be corrected.
From the tool's definition Tool name 'set_calendar' and description states it 'Configure[s] the calendar system' — configuration of game parameters is a reversible modification to game state.
Documented attack patterns abuse exactly the kind of access set_calendar 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 set_calendar:
{
"version": "1",
"default": "deny",
"tools": {
"set_calendar": {
"limits": [
{
"counter": "set_calendar_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_calendar 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.
Configure the calendar system for a game (months, days per month, hours per day, etc.). 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 set_calendar: 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.
set_calendar 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 set_calendar 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 set_calendar. 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.
set_calendar 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.