Pull latest changes for a repository on its target server.
AI agents invoke pull_repo to trigger actions in Komodo. 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.
Pulling latest changes from a remote repository triggers an external operation (git pull) on a target server. This is not a simple read — it modifies the working state of the repository on the server by fetching and merging/fast-forwarding remote changes, which can alter files, introduce new code, and affect running services.
From the tool's definition Pull latest changes for a repository on its target server
Documented attack patterns abuse exactly the kind of access pull_repo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Komodo, and nothing reaches the server without passing your rules. This is the rule we recommend for pull_repo:
{
"version": "1",
"default": "deny",
"tools": {
"pull_repo": {
"limits": [
{
"counter": "pull_repo_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}pull_repo 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.
Free to start. No card required.
Pull latest changes for a repository on its target server. It is categorised as a Execute tool in the Komodo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Komodo MCP server in PolicyLayer and add a rule for pull_repo: 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 Komodo. Nothing to install.
pull_repo is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pull_repo 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.
Set action: deny in the PolicyLayer policy for pull_repo. 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.
pull_repo is provided by the Komodo MCP server (myrikld/komodo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Komodo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
53 Komodo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.