ghost_node · Pinako AI Bridge MCP: Risk & Policy

WHAT IT DOES

What ghost_node does on Pinako AI Bridge

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

WHY IT NEEDS A POLICY

Why ghost_node needs a policy

An AI agent can call ghost_node faster than any human can review — one bad instruction and it creates or modifies resources in Pinako AI Bridge by the hundred, each call as confident as the last.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ghost_node Rate-limited

ghost_node 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": {
    "ghost_node": {
      "limits": [
        {
          "counter": "ghost_node_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 Pinako AI Bridge, so you can run agents against it safely.

FAQ

Questions about ghost_node

What does the ghost_node tool do? +

Closes the live browser tab(s) for this node and all live descendants, while preserving the tree node with chromeId=null on every ghosted node. Mirrors the manual. It is categorised as a Write tool in the Pinako AI Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ghost_node? +

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

What risk level is ghost_node? +

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

Can I rate-limit ghost_node? +

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

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

ghost_node is provided by the Pinako AI Bridge MCP server (teleomorph/pinako-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.