opencode_get_status

THE RISK

Low Risk

Why opencode_get_status needs a policy

This tool queries the status of the OpenCode CLI, which is a passive information retrieval operation with no side effects. It does not execute commands, modify data, delete anything, or perform any destructive actions. The low severity reflects the minimal risk profile of a simple status check operation.

From the tool's definition Tool name 'opencode_get_status' and description 'Check OpenCode CLI availability and status' indicate a read-only operation that retrieves status information without modifying or executing any code.

Documented attack patterns abuse exactly the kind of access opencode_get_status gives an agent:

POLICY

How to control opencode_get_status

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 opencode_get_status:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "opencode_get_status": {}
  }
}

opencode_get_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register OpenCode MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More OpenCode MCP Server tools

Execute execute_opencode_command Execute any OpenCode CLI command with full flexibility. Execute opencode_continue_session Continue an existing OpenCode session. Execute opencode_run Run OpenCode with a simple prompt message. Read opencode_list_models List available models in OpenCode. Read opencode_export_session Export an OpenCode session as JSON.

All 6 OpenCode MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about opencode_get_status

What does the opencode_get_status tool do? +

Check OpenCode CLI availability and status. It is categorised as a Read tool in the OpenCode MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on opencode_get_status? +

Register the OpenCode MCP Server MCP server in PolicyLayer and add a rule for opencode_get_status: 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.

What risk level is opencode_get_status? +

opencode_get_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit opencode_get_status? +

Yes. Add a rate_limit block to the opencode_get_status 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.

How do I block opencode_get_status completely? +

Set action: deny in the PolicyLayer policy for opencode_get_status. 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.

What MCP server provides opencode_get_status? +

opencode_get_status 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.

Enforce policy on every OpenCode MCP Server tool call.

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.

CHECK YOUR STACK →