Rewrites ad, social, email, or web copy into a lower-risk, more compliant version under Australian advertising law. Returns the rewritten copy, a list of changes made, and (optionally) suggested disclaimers. Indicative only — not legal advice. Always have a qualified compliance professional revie...
Risk signalsAccepts raw HTML/template content (content)
Part of the Anchor Compliance server.
Free to start. No card required.
AI agents call rewrite_content_compliant to retrieve information from Anchor Compliance 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 rewrite_content_compliant 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": {
"rewrite_content_compliant": {}
}
}See the full Anchor Compliance policy for all 4 tools.
These attack patterns abuse exactly the kind of access rewrite_content_compliant 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.
Rewrites ad, social, email, or web copy into a lower-risk, more compliant version under Australian advertising law. Returns the rewritten copy, a list of changes made, and (optionally) suggested disclaimers. Indicative only — not legal advice. Always have a qualified compliance professional review before publishing.. It is categorised as a Read tool in the Anchor Compliance MCP Server, which means it retrieves data without modifying state.
Register the Anchor Compliance MCP server in PolicyLayer and add a rule for rewrite_content_compliant: 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 Anchor Compliance. Nothing to install.
rewrite_content_compliant 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 rewrite_content_compliant 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 rewrite_content_compliant. 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.
rewrite_content_compliant is provided by the Anchor Compliance MCP server (joshuaogabriel/anchor-compliance). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Anchor Compliance 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.