submit_code · Quack MCP Server MCP: Risk & Policy

WHAT IT DOES

What submit_code does on Quack MCP Server

AI agents invoke submit_code to trigger actions in Quack MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why submit_code needs a policy

Submitting code for analysis triggers execution of external tools (linters, type checkers, test runners) against the provided code. While it doesn't directly execute arbitrary user code in a shell, it runs the submitted code through pytest which can execute arbitrary Python, making this an Execute-category action with high severity due to potential for running malicious code under the guise of testing/analysis.

From the tool's definition 'Submit Python code for analysis' — submits code to be run through analysis tools (pylint, mypy, pytest) as described in the server description

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_code Rate-limited

submit_code stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_code": {
      "limits": [
        {
          "counter": "submit_code_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Quack MCP Server, so you can run agents against it safely.

FAQ

Questions about submit_code

What does the submit_code tool do? +

Submit Python code for analysis. It is categorised as a Execute tool in the Quack MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on submit_code? +

Register the Quack MCP Server MCP server in PolicyLayer and add a rule for submit_code: 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 Quack MCP Server. Nothing to install.

What risk level is submit_code? +

submit_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit submit_code? +

Yes. Add a rate_limit block to the submit_code 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.

How do I block submit_code completely? +

Set action: deny in the PolicyLayer policy for submit_code. 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_code? +

submit_code is provided by the Quack MCP Server MCP server (smhajimirzaei/quack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.