curriculum_sync_push · Cluster Execution MCP Server MCP

WHAT IT DOES

What curriculum_sync_push does on Cluster Execution MCP Server

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

WHY IT NEEDS A POLICY

Why curriculum_sync_push needs a policy

The tool name suggests pushing/uploading curriculum data to the cluster (a sync push operation), which is a Write action. However, the description is empty, so the exact behavior is unknown. Given the cluster context and the paired 'pull' sibling tool, this likely synchronizes curriculum content to remote nodes.

From the tool's definition Tool name 'curriculum_sync_push' on a cluster execution server with sibling tools including 'curriculum_sync_pull' and 'cluster_bash'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

curriculum_sync_push Rate-limited

curriculum_sync_push 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": {
    "curriculum_sync_push": {
      "limits": [
        {
          "counter": "curriculum_sync_push_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 Cluster Execution MCP Server, so you can run agents against it safely.

FAQ

Questions about curriculum_sync_push

What does the curriculum_sync_push tool do? +

curriculum_sync_push. It is categorised as a Write tool in the Cluster Execution 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 curriculum_sync_push? +

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

What risk level is curriculum_sync_push? +

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

Can I rate-limit curriculum_sync_push? +

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

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

curriculum_sync_push is provided by the Cluster Execution MCP Server MCP server (marc-shade/cluster-execution-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.