AI agents use apply_quality_rules to create or update resources in Hi-AI — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hi-AI environment.
An AI agent can call apply_quality_rules faster than any human can review — one bad instruction and it creates or modifies resources in Hi-AI by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
apply rules|apply standards|apply rules|apply standards|follow conventions|apply - Apply quality rules. It is categorised as a Write tool in the Hi-AI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hi-AI MCP server in PolicyLayer and add a rule for apply_quality_rules: 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 Hi-AI. Nothing to install.
apply_quality_rules is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the apply_quality_rules 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 apply_quality_rules. 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.
apply_quality_rules is provided by the Hi-AI MCP server (ssdeanx/ssd-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.