submit_multi_plugin_job · Sage MCP Server MCP: Risk & Policy

WHAT IT DOES

What submit_multi_plugin_job does on Sage MCP Server

AI agents invoke submit_multi_plugin_job to trigger actions in Sage 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_multi_plugin_job needs a policy

The tool name strongly implies submitting a job involving multiple plugins to the Sage Grande Testbed. Submitting jobs triggers external operations on the testbed infrastructure. The description is empty, lowering confidence, but the name and server context clearly indicate job execution. Severity is high due to potential resource consumption and side effects on testbed nodes.

From the tool's definition Tool name 'submit_multi_plugin_job' combined with server context mentioning 'submit jobs' and 'manage Sage nodes'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_multi_plugin_job Rate-limited

submit_multi_plugin_job 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_multi_plugin_job": {
      "limits": [
        {
          "counter": "submit_multi_plugin_job_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 Sage MCP Server, so you can run agents against it safely.

FAQ

Questions about submit_multi_plugin_job

What does the submit_multi_plugin_job tool do? +

submit_multi_plugin_job. It is categorised as a Execute tool in the Sage 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_multi_plugin_job? +

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

What risk level is submit_multi_plugin_job? +

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

Can I rate-limit submit_multi_plugin_job? +

Yes. Add a rate_limit block to the submit_multi_plugin_job 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_multi_plugin_job completely? +

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

submit_multi_plugin_job is provided by the Sage MCP Server MCP server (waggle-sensor/sage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.