AI agents invoke validate_assignment_rule to trigger actions in ComplyOS. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name suggests it validates assignment rules, which likely involves executing a check or evaluation against compliance/LMS logic. Validation operations typically run logic against data, placing them in the Execute category. However, the description is empty, reducing confidence.
From the tool's definition Tool name 'validate_assignment_rule' and server context mentions 'validating assignment rules' as a core capability.
Attacks that exploit this kind of access
validate_assignment_rule. It is categorised as a Execute tool in the ComplyOS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ComplyOS MCP server in PolicyLayer and add a rule for validate_assignment_rule: 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.
validate_assignment_rule is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the validate_assignment_rule 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 validate_assignment_rule. 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.
validate_assignment_rule 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 →