sync_pull · Keshro MCP: Risk & Policy

WHAT IT DOES

What sync_pull does on Keshro MCP

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

WHY IT NEEDS A POLICY

Why sync_pull needs a policy

The description is empty and uninformative, which significantly lowers confidence. Based on the name 'sync_pull', this tool likely pulls or synchronizes data from an external source into the local project state. In the context of this MCP server (which manages plans, tasks, and integrations), a sync_pull likely fetches external data and updates local state — which is a Write operation (modifying local data).

From the tool's definition Tool name 'sync_pull' and empty description. The name suggests pulling/syncing data from an external source.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync_pull Rate-limited

sync_pull 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": {
    "sync_pull": {
      "limits": [
        {
          "counter": "sync_pull_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 Keshro MCP, so you can run agents against it safely.

FAQ

Questions about sync_pull

What does the sync_pull tool do? +

sync_pull. It is categorised as a Write tool in the Keshro MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sync_pull? +

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

What risk level is sync_pull? +

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

Can I rate-limit sync_pull? +

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

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

sync_pull is provided by the Keshro MCP server (jlewitt1/keshro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.