Merge action item updates
AI agents use action_item_tracker to create or update resources in ContextForge MCP Gateway — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ContextForge MCP Gateway environment.
The tool merges updates into action items, which is a write/modification operation on existing records. It is reversible in principle (updates can be overwritten), so Write is the most appropriate category. Severity is medium because misuse could corrupt or overwrite action item tracking data across potentially many records, but it is not inherently destructive or financial.
From the tool's definition 'Merge action item updates' — merging updates implies modifying existing data by combining or applying changes to action items.
Attacks that exploit this kind of access
Merge action item updates. It is categorised as a Write tool in the ContextForge MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for action_item_tracker: 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 ContextForge MCP Gateway. Nothing to install.
action_item_tracker 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 action_item_tracker 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 action_item_tracker. 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.
action_item_tracker is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). 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 →