AI agents call get_user_compliance_status to retrieve information from ComplyOS without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves compliance status information for a user. It performs a read-only operation with no side effects, no data modification, no code execution, and no irreversible actions. While the data retrieved may be sensitive (compliance records), the tool itself does not mutate state or trigger external operations.
From the tool's definition Tool name 'get_user_compliance_status' and description 'Get complete compliance status for a single user' indicate retrieval of existing compliance data with no modification, deletion, or execution of operations.
Attacks that exploit this kind of access
Get complete compliance status for a single user. It is categorised as a Read tool in the ComplyOS MCP Server, which means it retrieves data without modifying state.
Register the ComplyOS MCP server in PolicyLayer and add a rule for get_user_compliance_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 ComplyOS. Nothing to install.
get_user_compliance_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_user_compliance_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_user_compliance_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_user_compliance_status is provided by the ComplyOS MCP server (simongonzalezdc/complyos). 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 →