AI agents call check_ctd_completeness 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.
check_ctd_completeness retrieves and analyzes compliance status without creating, modifying, or destroying data. It returns informational results (gap identification) to inform regulatory submission decisions. No irreversible changes, financial transactions, or arbitrary code execution are involved.
From the tool's definition Tool performs validation/comparison of provided CTD sections against requirements to 'identify gaps' — a read-only analytical operation with no data modification, deletion, or external side effects.
Attacks that exploit this kind of access
Check a list of provided CTD sections against required sections and identify gaps. 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_ctd_completeness: 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_ctd_completeness 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_ctd_completeness 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_ctd_completeness. 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_ctd_completeness 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.
check_ctd_completeness is one line of Regsub's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →