GET /v1/company/enrich/{job_id}/status. Poll until status is
AI agents call get_company_enrichment_result 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 status information about an existing enrichment job. It performs no modifications, deletions, or external state changes—it only queries and returns job status data. This is a classic Read operation with low severity, as misuse would only expose information about enrichment jobs rather than causing data loss, financial impact, or unauthorized modifications.
From the tool's definition Tool name 'get_company_enrichment_result' and description 'GET /v1/company/enrich/{job_id}/status. Poll until status is' indicate a read operation that retrieves the status of a company enrichment job.
Attacks that exploit this kind of access
GET /v1/company/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_company_enrichment_result: 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_company_enrichment_result 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_company_enrichment_result 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_company_enrichment_result. 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_company_enrichment_result 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 →