Run only the configured typecheck command, when one is configured.
AI agents invoke repo.run_typecheck to trigger actions in ForLoop MCP. 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.
This tool invokes an external command (typecheck) on a code repository. While typecheck operations are generally safe in intent, they represent code execution that could be maliciously configured or exploited if a repository's configuration is compromised. The blast radius is high because a compromised typecheck command could execute arbitrary logic.
From the tool's definition Tool runs a configured typecheck command, which executes arbitrary code/scripts defined in the repository's configuration.
Attacks that exploit this kind of access
Run only the configured typecheck command, when one is configured. It is categorised as a Execute tool in the ForLoop MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ForLoop MCP server in PolicyLayer and add a rule for repo.run_typecheck: 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 ForLoop MCP. Nothing to install.
repo.run_typecheck 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 repo.run_typecheck 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 repo.run_typecheck. 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.
repo.run_typecheck is provided by the ForLoop MCP server (master0ffate/forloop-mcp). 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 →