reject_entity_match_tool · Reltio MCP Server MCP

WHAT IT DOES

What reject_entity_match_tool does on Reltio MCP Server

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

WHY IT NEEDS A POLICY

Why reject_entity_match_tool needs a policy

The tool performs a state modification ('reject') on entity matches within Reltio's MDM platform. This is a Write-category action because it alters data (match status) reversibly—rejections can be undone or matches re-evaluated. It is not Destructive (match records are not deleted), not Execute (no arbitrary code/commands), and not Financial.

From the tool's definition Tool name 'reject_entity_match_tool' indicates it modifies match state in a master data management system. Sibling tools include 'find_potential_matches_tool' (Read) and other entity/relationship operations (Write/Destructive).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reject_entity_match_tool Rate-limited

reject_entity_match_tool 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": {
    "reject_entity_match_tool": {
      "limits": [
        {
          "counter": "reject_entity_match_tool_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 Reltio MCP Server, so you can run agents against it safely.

FAQ

Questions about reject_entity_match_tool

What does the reject_entity_match_tool tool do? +

reject_entity_match_tool. It is categorised as a Write tool in the Reltio MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on reject_entity_match_tool? +

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

What risk level is reject_entity_match_tool? +

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

Can I rate-limit reject_entity_match_tool? +

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

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

reject_entity_match_tool is provided by the Reltio MCP Server MCP server (reltio-ai/reltio-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.