AI agents call check_ich_compliance to retrieve information from Regsub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only analytical tool that evaluates compliance by comparing input against regulatory guidelines and returns assessment results. There are no side effects, no data modification, no code execution, and no irreversible actions. The blast radius of misuse is minimal—an incorrect compliance assessment might lead to poor regulatory decisions, but the tool itself cannot corrupt systems or data.
From the tool's definition Tool 'check_ich_compliance' performs a compliance assessment by checking documents/studies against ICH guideline requirements. The verb 'check' and the return of an 'assessment' indicate data retrieval and analysis with no modification of systems or data.
Attacks that exploit this kind of access
Check a description of a study or document against ICH guideline requirements and return a compliance assessment. It is categorised as a Read tool in the Regsub MCP Server, which means it retrieves data without modifying state.
Register the Regsub MCP server in PolicyLayer and add a rule for check_ich_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 Regsub. Nothing to install.
check_ich_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_ich_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_ich_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_ich_compliance is provided by the Regsub MCP server (pubspro/regsub-mcp). 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 →