Spawn Semgrep + Betterleaks + OSV-Scanner (+ Bandit/Biome when the project profile supports them), merge their SARIF outputs, write
AI agents invoke scan to trigger actions in OpenCodeHub 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.
This tool executes multiple external security scanning tools (Semgrep, Betterleaks, OSV-Scanner, Bandit, Biome) as subprocesses, merges their SARIF outputs, and writes results. Spawning external processes falls squarely in the Execute category.
From the tool's definition 'Spawn Semgrep + Betterleaks + OSV-Scanner (+ Bandit/Biome when the project profile supports them)' — explicitly spawns/executes multiple external scanning processes
Attacks that exploit this kind of access
Spawn Semgrep + Betterleaks + OSV-Scanner (+ Bandit/Biome when the project profile supports them), merge their SARIF outputs, write. It is categorised as a Execute tool in the OpenCodeHub MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OpenCodeHub MCP Server MCP server in PolicyLayer and add a rule for scan: 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 OpenCodeHub MCP Server. Nothing to install.
scan 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 scan 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 scan. 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.
scan is provided by the OpenCodeHub MCP Server MCP server (theagenticguy/opencodehub). 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 →