Execute any OpenCode CLI command with full flexibility.
AI agents invoke execute_opencode_command to trigger actions in OpenCode 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.
The tool allows execution of arbitrary OpenCode CLI commands with unrestricted flexibility. Since OpenCode is a coding agent that runs terminal-based tasks, this tool provides the ability to execute code and shell commands whose effects depend entirely on the arguments passed. This poses critical risk: an AI agent could execute malicious commands, exfiltrate data, modify system state, or compromise security.
From the tool's definition Tool description states 'Execute any OpenCode CLI command with full flexibility.' The server integrates a coding agent that executes 'terminal-based coding tasks' and provides tools for 'running commands.' This enables arbitrary command execution via the…
Documented attack patterns abuse exactly the kind of access execute_opencode_command gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenCode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_opencode_command:
{
"version": "1",
"default": "deny",
"tools": {
"execute_opencode_command": {
"limits": [
{
"counter": "execute_opencode_command_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_opencode_command 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.
Execute any OpenCode CLI command with full flexibility. It is categorised as a Execute tool in the OpenCode MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OpenCode MCP Server MCP server in PolicyLayer and add a rule for execute_opencode_command: 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 OpenCode MCP Server. Nothing to install.
execute_opencode_command 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 execute_opencode_command 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 execute_opencode_command. 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.
execute_opencode_command is provided by the OpenCode MCP Server MCP server (nosolosoft/opencode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenCode MCP Server, 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.
6 OpenCode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.