Submit a complete plan XML to Overture. IMPORTANT: Call get_usage_instructions first to learn the correct XML format and workflow. Use this if you have the entire plan ready at once. The plan will be parsed and displayed on the canvas.
AI agents use submit_plan to create or update resources in Overture — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Overture environment.
submit_plan creates or modifies plan state in Overture by accepting and storing plan XML. This is reversible (plans can presumably be updated or deleted via other tools like plan_failed or check_rerun). It does not execute arbitrary code, trigger external operations beyond visualization, or delete data irreversibly.
From the tool's definition Tool description states 'Submit a complete plan XML to Overture' and 'The plan will be parsed and displayed on the canvas.' This is a create/modify operation that writes plan data to the system.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access submit_plan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Overture, and nothing reaches the server without passing your rules. This is the rule we recommend for submit_plan:
{
"version": "1",
"default": "deny",
"tools": {
"submit_plan": {
"limits": [
{
"counter": "submit_plan_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}submit_plan 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.
Submit a complete plan XML to Overture. IMPORTANT: Call get_usage_instructions first to learn the correct XML format and workflow. Use this if you have the entire plan ready at once. The plan will be parsed and displayed on the canvas. It is categorised as a Write tool in the Overture MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Overture MCP server in PolicyLayer and add a rule for submit_plan: 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 Overture. Nothing to install.
submit_plan 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_plan 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_plan. 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_plan is provided by the Overture MCP server (sixhq/overture). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Overture tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Overture tools catalogued and risk-classified — across an index of 42,500+ MCP servers.