merge_compounds · Scifinder Route MCP: Risk & Policy

WHAT IT DOES

What merge_compounds does on Scifinder Route

AI agents use merge_compounds to create or update resources in Scifinder Route — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scifinder Route environment.

WHY IT NEEDS A POLICY

Why merge_compounds needs a policy

This tool creates or modifies data by consolidating compound aliases and reaction links, characteristic of a Write operation. While reversible, merging compounds could have significant downstream effects on research data integrity and searchability, warranting high severity.

From the tool's definition Merge source compound aliases/reaction links into a target compound. The verb 'merge' modifies data (consolidates multiple compound records into one), which is a reversible alteration of the database state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_compounds Rate-limited

merge_compounds 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": {
    "merge_compounds": {
      "limits": [
        {
          "counter": "merge_compounds_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 Scifinder Route, so you can run agents against it safely.

FAQ

Questions about merge_compounds

What does the merge_compounds tool do? +

Merge source compound aliases/reaction links into a target compound. It is categorised as a Write tool in the Scifinder Route 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_compounds? +

Register the Scifinder Route MCP server in PolicyLayer and add a rule for merge_compounds: 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 Scifinder Route. Nothing to install.

What risk level is merge_compounds? +

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

Can I rate-limit merge_compounds? +

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

Set action: deny in the PolicyLayer policy for merge_compounds. 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_compounds? +

merge_compounds is provided by the Scifinder Route MCP server (kettly1260/scifinder-route-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.