Medium Risk

merge_history

Track merge conflict resolution audit trail

Records merge decisions

Part of the Aifp MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

aifp Write Risk 3/5

AI agents use merge_history to create or modify resources in Aifp. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call merge_history repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Aifp.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-aryanduntley-aifp.yaml
tools:
  merge_history:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Aifp policy for all 24 tools.

Tool Name merge_history
Category Write
MCP Server Aifp MCP Server
Risk Level Medium

View all 24 tools →

Agents calling write-class tools like merge_history have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the merge_history tool do? +

Track merge conflict resolution audit trail. It is categorised as a Write tool in the Aifp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on merge_history? +

Add a rule in your Intercept YAML policy under the tools section for merge_history. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aifp MCP server.

What risk level is merge_history? +

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

Can I rate-limit merge_history? +

Yes. Add a rate_limit block to the merge_history rule in your Intercept 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 merge_history completely? +

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

merge_history is provided by the Aifp MCP server (aifp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Aifp

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.