Create a new quest. Call this whenever the player receives a mission, task, or goal - whether from an NPC, discovered through exploration, or self-initiated. Include clear objectives that can be tracked.
AI agents use create_quest 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 performs a data creation operation within the game state management system. Creating a quest adds a new record to the game's quest tracking system but does not execute arbitrary code, delete data irreversibly, or impact real systems. The severity is low because misuse would only affect the fictional game state with no blast radius beyond the RPG session.
From the tool's definition Tool description explicitly states 'Create a new quest', which is a create operation that modifies game state by adding a new quest object. This is reversible (quests can be abandoned or deleted) and has no real-world side effects.
Documented attack patterns abuse exactly the kind of access create_quest 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_quest:
{
"version": "1",
"default": "deny",
"tools": {
"create_quest": {
"limits": [
{
"counter": "create_quest_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_quest 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 new quest. Call this whenever the player receives a mission, task, or goal - whether from an NPC, discovered through exploration, or self-initiated. Include clear objectives that can be tracked. 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_quest: 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_quest 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_quest 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_quest. 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_quest 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.