Manage RPG quests - creation, assignment, progress, and completion. Actions: create, get, list, assign, update_objective, complete_objective, complete, get_log Aliases: new→create, accept→assign, progress→update_objective, finish→complete, log→get_log 📜 QUEST WORKFLOW: 1. create - Define a quest...
AI agents use quest_manage to create or update resources in Rpg — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rpg environment.
The tool primarily creates and updates quest records (create, assign, update_objective, complete_objective, complete). While these are reversible modifications to game state rather than irreversible deletions, they go beyond reading data to actively modify the game world.
From the tool's definition Tool description states 'Manage RPG quests - creation, assignment, progress, and completion' with actions including create, assign, update_objective, complete_objective, complete.
Documented attack patterns abuse exactly the kind of access quest_manage gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rpg, and nothing reaches the server without passing your rules. This is the rule we recommend for quest_manage:
{
"version": "1",
"default": "deny",
"tools": {
"quest_manage": {
"limits": [
{
"counter": "quest_manage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}quest_manage 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.
Manage RPG quests - creation, assignment, progress, and completion. Actions: create, get, list, assign, update_objective, complete_objective, complete, get_log Aliases: new→create, accept→assign, progress→update_objective, finish→complete, log→get_log 📜 QUEST WORKFLOW: 1. create - Define a quest with objectives and rewards 2. assign - Character accepts the quest 3. update_objective - Track progress on objectives (requires characterId) 4. complete_objective - Mark objectives done 5. complete - Turn in quest for rewards 6. get_log - View character. It is categorised as a Write tool in the Rpg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rpg MCP server in PolicyLayer and add a rule for quest_manage: 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 Rpg. Nothing to install.
quest_manage 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 quest_manage 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 quest_manage. 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.
quest_manage is provided by the Rpg MCP server (mnehmos/mnehmos.rpg.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rpg, 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.
47 Rpg tools catalogued and risk-classified — across an index of 43,000+ MCP servers.