Sync a plan document
AI agents use ralph_hero__sync_plan_graph to create or update resources in Ralph Hero — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ralph Hero environment.
The verb 'sync' implies bidirectional or unidirectional synchronization, which creates or modifies plan data. This is a Write-category action because it updates plan information reversibly. Severity is medium because it affects workflow data but is not destructive or financial; confidence is moderate (0.75) because the description lacks implementation details that would clarify exact scope and side effects.
From the tool's definition Tool is called 'sync_plan_graph' and description states 'Sync a plan document' – syncing typically involves modifying or updating data (a reversible write operation) rather than merely reading it.
Attacks that exploit this kind of access
Sync a plan document. It is categorised as a Write tool in the Ralph Hero MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ralph Hero MCP server in PolicyLayer and add a rule for ralph_hero__sync_plan_graph: 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 Ralph Hero. Nothing to install.
ralph_hero__sync_plan_graph 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 ralph_hero__sync_plan_graph 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 ralph_hero__sync_plan_graph. 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.
ralph_hero__sync_plan_graph is provided by the Ralph Hero MCP server (ralph-hero-mcp-server). 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 →