Clona un repositorio de GitHub en una carpeta local permitida.
AI agents invoke clonar_proyecto_github to trigger actions in Modular 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.
Cloning a GitHub repository executes a git clone operation that downloads and writes files to the local filesystem. It is an external operation with side effects (creates files/directories locally), making it Execute. It is not purely destructive or financial, but it does trigger an external git operation whose effects depend on the repository argument.
From the tool's definition Clona un repositorio de GitHub en una carpeta local permitida
Attacks that exploit this kind of access
Clona un repositorio de GitHub en una carpeta local permitida. It is categorised as a Execute tool in the Modular MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Modular MCP Server MCP server in PolicyLayer and add a rule for clonar_proyecto_github: 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 Modular MCP Server. Nothing to install.
clonar_proyecto_github 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 clonar_proyecto_github 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 clonar_proyecto_github. 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.
clonar_proyecto_github is provided by the Modular MCP Server MCP server (satanas66/tfm-mcp-062026). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →