indent_node · Pinako AI Bridge MCP: Risk & Policy

WHAT IT DOES

What indent_node does on Pinako AI Bridge

AI agents use indent_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 indent_node needs a policy

The tool creates a reversible modification to data structure by changing parent-child relationships within tab/library/bookmark hierarchies. This is a Write operation (modifies data organization), not Destructive since the action can be undone by un-indenting.

From the tool's definition Tool description states it 'Nests a node under its previous sibling' and 'Auto-expands the new parent', indicating it modifies the hierarchical structure of tabs, libraries, and bookmarks by moving and reorganizing elements.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

indent_node Rate-limited

indent_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": {
    "indent_node": {
      "limits": [
        {
          "counter": "indent_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 indent_node

What does the indent_node tool do? +

Nests a node under its previous sibling (one level deeper). Rejects when the node has no prior sibling (INDENT_NO_PREV_SIBLING). Auto-expands the new parent. Works across tree, library, and bookmark scopes — a common pattern for quickly de-nesting then re-organizing tabs. For scope=. 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 indent_node? +

Register the Pinako AI Bridge MCP server in PolicyLayer and add a rule for indent_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 indent_node? +

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

Can I rate-limit indent_node? +

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

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

indent_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.