AI agents use submit_validation_result 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 creates or updates validation records in the gamified development system, affecting quest completion status and reward eligibility. It is Write-category because it modifies data reversibly (validation results can theoretically be corrected or resubmitted).
From the tool's definition Tool 'submit_validation_result' records (creates/modifies) validation results in local storage. Description states it records validation outcomes, which modifies the state of quest progress tracking and XP eligibility.
Attacks that exploit this kind of access
Record a validation result from a real command the agent or user already ran. 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 submit_validation_result: 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.
submit_validation_result 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 submit_validation_result 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 submit_validation_result. 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.
submit_validation_result 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →