origin_of

THE RISK

Low Risk

Why origin_of needs a policy

This tool retrieves historical context about a decision's origin within the knowledge base. It performs a read-only lookup operation without creating, modifying, deleting, or executing any code. The severity is low because reading stored metadata about decision origins poses minimal risk of misuse by an AI agent.

From the tool's definition Tool description states 'Return the M1 origin block attached to a decision' — a retrieval operation with no modification or side effects. The verb 'return' indicates data query functionality.

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

POLICY

How to control origin_of

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

policy.json

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

origin_of 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 Codevira 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 Codevira MCP tools

Write consensus_propose_supersession v3.1.0 M7 Phase C: Open a cross-IDE supersession proposal. Write defer_phase Move an upcoming phase to the deferred list. Write reaffirm_decision v3.2.0: refresh a do_not_revert decision Write record_skill v3.1.0 M3: Author a new skill in the canonical store Write refresh_graph Auto-generate context graph nodes for new or unregistered files. Write supersede_decision v2.1.2 Item 26: retire old_id and link to a replacement. Write supersede_skill v3.1.0 M3: Version a skill. Writes a new skill that supersedes Write add_phase Add a new upcoming phase to the roadmap.

All 48 Codevira 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 origin_of

What does the origin_of tool do? +

v3.1.0 M7: Return the M1 origin block attached to a decision. It is categorised as a Read tool in the Codevira MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on origin_of? +

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

What risk level is origin_of? +

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

Can I rate-limit origin_of? +

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

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

origin_of is provided by the Codevira MCP server (sachinshelke/codevira). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Codevira MCP tool call.

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

CHECK YOUR STACK →