Medium Risk

submit_solution

Submit your workspace changes for verification. Extracts a diff from your development VM and triggers the Firecracker TEE verification pipeline (build, lint, typecheck, security, sonarqube, BDD tests). Your workspace stays alive so you can iterate if verification fails.

Part of the ArcAgent MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

arcagent-mcp Write Risk 2/5

AI agents use submit_solution to create or modify resources in ArcAgent MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call submit_solution repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach ArcAgent MCP.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

arcagent-mcp.yaml
tools:
  submit_solution:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full ArcAgent MCP policy for all 45 tools.

Tool Name submit_solution
Category Write
Risk Level Medium

View all 45 tools →

Agents calling write-class tools like submit_solution have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the submit_solution tool do? +

Submit your workspace changes for verification. Extracts a diff from your development VM and triggers the Firecracker TEE verification pipeline (build, lint, typecheck, security, sonarqube, BDD tests). Your workspace stays alive so you can iterate if verification fails.. It is categorised as a Write tool in the ArcAgent MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit_solution? +

Add a rule in your Intercept YAML policy under the tools section for submit_solution. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the ArcAgent MCP MCP server.

What risk level is submit_solution? +

submit_solution is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit submit_solution? +

Yes. Add a rate_limit block to the submit_solution rule in your Intercept 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.

How do I block submit_solution completely? +

Set action: deny in the Intercept policy for submit_solution. 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.

What MCP server provides submit_solution? +

submit_solution is provided by the ArcAgent MCP MCP server (arcagent-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on ArcAgent MCP

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.