Set the main title of a graph with configurable font size, bold, and position.
AI agents use tool_set_graph_title to create or update resources in origin-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your origin-MCP environment.
This tool creates or modifies graph presentation attributes without side effects beyond the graph itself. Changes are easily reversible (title can be changed again or cleared). This is a typical Write operation: it alters state in the visualization but does not execute arbitrary code, delete data, or cause irreversible harm.
From the tool's definition tool_set_graph_title modifies graph properties (title, font size, bold, position) — a reversible change to visualization metadata. The description explicitly states it 'Set[s] the main title' with configurable styling options.
Attacks that exploit this kind of access
Set the main title of a graph with configurable font size, bold, and position. It is categorised as a Write tool in the origin-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the origin- MCP server in PolicyLayer and add a rule for tool_set_graph_title: 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 origin-MCP. Nothing to install.
tool_set_graph_title is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tool_set_graph_title 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.
Set action: deny in the PolicyLayer policy for tool_set_graph_title. 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.
tool_set_graph_title is provided by the origin- MCP server (zhang-923-ze/origin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →