GET /v1/contact/enrich/{job_id}/status. Poll until status is
AI agents call get_contact_enrich_status to retrieve information from DataMerge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the status of an enrichment job without modifying, executing operations, deleting data, or affecting financial systems. It is a simple query operation that returns job status information. The low severity reflects minimal blast radius—status polling cannot cause harm even if misused by an AI agent.
From the tool's definition Tool name 'get_contact_enrich_status' and description indicate polling a status endpoint (GET /v1/contact/enrich/{job_id}/status). The 'GET' HTTP method and 'status' retrieval operation are pure read operations with no side effects.
Attacks that exploit this kind of access
GET /v1/contact/enrich/{job_id}/status. Poll until status is. It is categorised as a Read tool in the DataMerge MCP MCP Server, which means it retrieves data without modifying state.
Register the DataMerge MCP server in PolicyLayer and add a rule for get_contact_enrich_status: 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 DataMerge MCP. Nothing to install.
get_contact_enrich_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_contact_enrich_status 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 get_contact_enrich_status. 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.
get_contact_enrich_status is provided by the DataMerge MCP server (poolside-ventures/datamerge-mcp). 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 →