Record a firm's intent to claim its directory listing. Pre-OAuth this does NOT automatically grant control of the listing. TESSA logs the claim and a representative reaches out via email within one business day to verify the claimant and switch the listing's verification status to 'claimed'. The ...
Part of the Compliance Registry server.
Free to start. No card required.
AI agents call claim_listing to retrieve information from Compliance Registry without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though claim_listing only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"claim_listing": {}
}
}See the full Compliance Registry policy for all 10 tools.
These attack patterns abuse exactly the kind of access claim_listing gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Record a firm's intent to claim its directory listing. Pre-OAuth this does NOT automatically grant control of the listing. TESSA logs the claim and a representative reaches out via email within one business day to verify the claimant and switch the listing's verification status to 'claimed'. The full self-service OAuth-2.1 claim flow lands in a follow-up plan.. It is categorised as a Read tool in the Compliance Registry MCP Server, which means it retrieves data without modifying state.
Register the Compliance Registry MCP server in PolicyLayer and add a rule for claim_listing: 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 Compliance Registry. Nothing to install.
claim_listing 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 claim_listing 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 claim_listing. 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.
claim_listing is provided by the Compliance Registry MCP server (globalpart/tessa-aios). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Compliance Registry tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.