AI agents use start_quest to create or update resources in Idelrpg — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Idelrpg environment.
This tool modifies the state of an existing quest by changing its status to active. It is a reversible state change (write operation) with no destructive, financial, or execution implications. Since it operates on local game data, the blast radius of misuse is minimal.
From the tool's definition Mark a created quest active
Attacks that exploit this kind of access
Mark a created quest active. It is categorised as a Write tool in the Idelrpg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Idelrpg MCP server in PolicyLayer and add a rule for start_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 Idelrpg. Nothing to install.
start_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 start_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 start_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.
start_quest is provided by the Idelrpg MCP server (jrslyce/idelrpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
start_quest is one line of Idelrpg's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →