AI agents call list_intake 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.
Based on naming convention, 'list_intake' most likely retrieves or queries intake records (consistent with the server's compliance auditing context). Without a description, confidence is moderate, but the 'list' prefix strongly indicates a read operation with no side effects. Given the compliance auditing domain, this would retrieve intake scope or configuration data without modifying it.
From the tool's definition Tool name 'list_intake' follows the 'list_*' pattern which conventionally retrieves or enumerates data without modification. Exact description is empty, limiting definitive assessment.
Attacks that exploit this kind of access
list_intake. 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 list_intake: 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.
list_intake 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 list_intake 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 list_intake. 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.
list_intake 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 →