content_queue · Personal Brain MCP: Risk & Policy

WHAT IT DOES

What content_queue does on Personal Brain

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

WHY IT NEEDS A POLICY

Why content_queue needs a policy

This tool primarily enables creating and updating entries in a personal content queue. Adding items and updating watch status are both write operations that modify data. While it also supports reading (get filtered queue), the action words 'add new items' and 'mark watched' indicate write capabilities. No deletion, code execution, or financial operations are involved.

From the tool's definition The tool can 'add new items' and 'mark watched', which are reversible write operations that create or modify data in a personal queue.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

content_queue Rate-limited

content_queue 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": {
    "content_queue": {
      "limits": [
        {
          "counter": "content_queue_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 Personal Brain, so you can run agents against it safely.

FAQ

Questions about content_queue

What does the content_queue tool do? +

Saved videos/podcasts/articles to consume later. Get filtered queue (optionally by max duration — great for picking something to watch on a treadmill), add new items, or mark watched. It is categorised as a Write tool in the Personal Brain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on content_queue? +

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

What risk level is content_queue? +

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

Can I rate-limit content_queue? +

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

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

content_queue is provided by the Personal Brain MCP server (phantomts/personal-brain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.