ingest_rune_manifest · Semantic Context MCP: Risk & Policy

WHAT IT DOES

What ingest_rune_manifest does on Semantic Context MCP

AI agents use ingest_rune_manifest to create or update resources in Semantic Context MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Semantic Context MCP environment.

WHY IT NEEDS A POLICY

Why ingest_rune_manifest needs a policy

The tool ingests/imports a manifest file and saves each binding intent annotation as a new context entry. This is a write operation — it creates multiple context records in the system. It does not appear to execute code or irreversibly delete data.

From the tool's definition 'Import a rune.schema.json manifest — saves each binding intent annotation as a Wake context'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ingest_rune_manifest Rate-limited

ingest_rune_manifest stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ingest_rune_manifest": {
      "limits": [
        {
          "counter": "ingest_rune_manifest_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Semantic Context MCP, so you can run agents against it safely.

FAQ

Questions about ingest_rune_manifest

What does the ingest_rune_manifest tool do? +

Import a rune.schema.json manifest — saves each binding intent annotation as a Wake context, connecting Rune governance to Wake causal memory. It is categorised as a Write tool in the Semantic Context MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ingest_rune_manifest? +

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

What risk level is ingest_rune_manifest? +

ingest_rune_manifest is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ingest_rune_manifest? +

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

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

ingest_rune_manifest is provided by the Semantic Context MCP server (semanticintent/semantic-wake-intelligence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.