Check if digital content is protected with ProofX. Returns the creator, protection date, signature status, and content details. Use this when a user wants to verify if an image, video, or document has been registered with ProofX.
Part of the ProofX - Content Protection for Creators server.
Free to start. No card required.
AI agents call verify_content to retrieve information from ProofX - Content Protection for Creators 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 verify_content 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": {
"verify_content": {}
}
}See the full ProofX - Content Protection for Creators policy for all 6 tools.
These attack patterns abuse exactly the kind of access verify_content 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.
Check if digital content is protected with ProofX. Returns the creator, protection date, signature status, and content details. Use this when a user wants to verify if an image, video, or document has been registered with ProofX.. It is categorised as a Read tool in the ProofX - Content Protection for Creators MCP Server, which means it retrieves data without modifying state.
Register the ProofX - Content Protection for Creators MCP server in PolicyLayer and add a rule for verify_content: 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 ProofX - Content Protection for Creators. Nothing to install.
verify_content 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 verify_content 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 verify_content. 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.
verify_content is provided by the ProofX - Content Protection for Creators MCP server (https://proofx-mcp.fly.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 ProofX - Content Protection for Creators 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.