Compliance signals for one provider: LegitScript certification, state-license record, FDA warning-letter screen — each with status, source and verification timestamp. These are PAID fields. Without XCIRCL_API_KEY the tool still answers (provider identity + compliance: null) and explains how to un...
AI agents call check_compliance to retrieve information from Xcircl Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval tool that queries compliance verification records. It has no side effects, does not modify data, does not execute code or commands, and does not perform irreversible operations. The access control (API key required for full data) is an entitlement restriction, not a functional classification change.
From the tool's definition Tool retrieves and queries compliance signal data (LegitScript certification, state-license record, FDA warning-letter screen) with status, source, and timestamp.
Attacks that exploit this kind of access
Compliance signals for one provider: LegitScript certification, state-license record, FDA warning-letter screen — each with status, source and verification timestamp. These are PAID fields. Without XCIRCL_API_KEY the tool still answers (provider identity + compliance: null) and explains how to unlock:. It is categorised as a Read tool in the Xcircl Agent MCP Server, which means it retrieves data without modifying state.
Register the Xcircl Agent MCP server in PolicyLayer and add a rule for check_compliance: 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 Xcircl Agent. Nothing to install.
check_compliance 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 check_compliance 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 check_compliance. 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.
check_compliance is provided by the Xcircl Agent MCP server (25cy/xcircl-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
check_compliance is one line of Xcircl Agent's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →