source.resume · Lore Context MCP: Risk & Policy

WHAT IT DOES

What source.resume does on Lore Context

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

WHY IT NEEDS A POLICY

Why source.resume needs a policy

The tool writes an active heartbeat to resume a capture source, which is a state-modification operation (Write). It creates/updates state on the server but does not delete data or execute arbitrary code. Misuse could disrupt or improperly activate data capture pipelines, hence medium severity.

From the tool's definition Resume a hosted capture source by writing an active heartbeat

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

source.resume Rate-limited

source.resume 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": {
    "source.resume": {
      "limits": [
        {
          "counter": "source.resume_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 Lore Context, so you can run agents against it safely.

FAQ

Questions about source.resume

What does the source.resume tool do? +

Resume a hosted capture source by writing an active heartbeat. It is categorised as a Write tool in the Lore Context MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on source.resume? +

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

What risk level is source.resume? +

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

Can I rate-limit source.resume? +

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

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

source.resume is provided by the Lore Context MCP server (Lore-Context/lore-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.