get_workplan

THE RISK

Low Risk

Why get_workplan needs a policy

This tool performs data retrieval only. It fetches existing workplan/issue content without side effects, matching the Read category definition. The blast radius is minimal since it only accesses information already stored in the system. No destructive, financial, write, or code execution capabilities are present.

From the tool's definition Tool 'retrieves the workplan content' for a specified issue number - a straightforward query operation with no modification, deletion, or execution capability.

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

POLICY

How to control get_workplan

PolicyLayer is an MCP gateway — it sits between your AI agents and Yellhorn MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_workplan:

policy.json

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

get_workplan 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 Yellhorn MCP — 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 Yellhorn MCP tools

Write create_workplan create_workplan Write revise_workplan revise_workplan Other curate_context curate_context Other judge_workplan judge_workplan

All 5 Yellhorn MCP 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 get_workplan

What does the get_workplan tool do? +

Retrieves the workplan content (GitHub issue body) for a specified issue number. It is categorised as a Read tool in the Yellhorn MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workplan? +

Register the Yellhorn MCP server in PolicyLayer and add a rule for get_workplan: 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 Yellhorn MCP. Nothing to install.

What risk level is get_workplan? +

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

Can I rate-limit get_workplan? +

Yes. Add a rate_limit block to the get_workplan 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 get_workplan completely? +

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

get_workplan is provided by the Yellhorn MCP server (msnidal/yellhorn-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Yellhorn MCP tool call.

Start from Yellhorn MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →