submit_task · Cross-Project MCP Server MCP: Risk & Policy

WHAT IT DOES

What submit_task does on Cross-Project MCP Server

AI agents use submit_task to create or update resources in Cross-Project MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cross-Project MCP Server environment.

WHY IT NEEDS A POLICY

Why submit_task needs a policy

This tool creates new task entries and delegates work, which are reversible write operations. It does not execute code directly (Execute category), delete data (Destructive), or move money (Financial). The severity is medium because delegating work across codebases could create unintended tasks, duplicate efforts, or consume resources, but the effects are reversible via task cancellation or modification.

From the tool's definition Tool name 'submit_task' combined with description 'DELEGATE work to this repository' indicates the tool creates or modifies task records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_task Rate-limited

submit_task 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_task": {
      "limits": [
        {
          "counter": "submit_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about submit_task

What does the submit_task tool do? +

DELEGATE work to this repository. It is categorised as a Write tool in the Cross-Project MCP Server 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_task? +

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

What risk level is submit_task? +

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

Can I rate-limit submit_task? +

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

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

submit_task is provided by the Cross-Project MCP Server MCP server (sweetsrepo/cross-project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.