curriculum_sync_pull · Cluster Execution MCP Server MCP

WHAT IT DOES

What curriculum_sync_pull does on Cluster Execution MCP Server

AI agents invoke curriculum_sync_pull to trigger actions in Cluster Execution 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 curriculum_sync_pull needs a policy

The tool name suggests a pull/sync operation for curriculum data across cluster nodes. Given the server context (distributed execution, SSH, cluster management) and sibling tool 'curriculum_sync_push', this likely triggers a remote synchronization operation across nodes, which falls under Execute. However, 'pull' could also be a read/fetch operation. Confidence is lowered due to empty description.

From the tool's definition Tool name 'curriculum_sync_pull' on a cluster execution server with sibling tools like 'cluster_bash', 'broadcast_to_cluster', and 'curriculum_sync_push'. Description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

curriculum_sync_pull Rate-limited

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

FAQ

Questions about curriculum_sync_pull

What does the curriculum_sync_pull tool do? +

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

Register the Cluster Execution MCP Server MCP server in PolicyLayer and add a rule for curriculum_sync_pull: 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_pull? +

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

Can I rate-limit curriculum_sync_pull? +

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

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

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