This record as markdown: /tools/hermoso/check-ad-policy.md
What check_ad_policy does on Hermoso
AI agents call check_ad_policy to retrieve information from Hermoso without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_ad_policy is rated Low
This tool appears to be a policy compliance checker that analyzes ad copy before submission—a read-only validation operation. It retrieves or queries policy rules and returns compliance feedback without creating, modifying, executing external commands, or deleting anything. The side effect is informational only.
From the tool's definition Tool name 'check_ad_policy' and description 'Pre-flight ad copy against Meta' indicate validation/checking functionality against Meta's ad policy guidelines.
Attacks that exploit this kind of access
The rule that runs check_ad_policy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hermoso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_ad_policy, this is the rule to start with:
check_ad_policy is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hermoso, apply this rule, and every check_ad_policy call is checked against it from then on.
Questions about check_ad_policy
Pre-flight ad copy against Meta. It is categorised as a Read tool in the Hermoso MCP Server, which means it retrieves data without modifying state.
Register the Hermoso MCP server in PolicyLayer and add a rule for check_ad_policy: 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 Hermoso. Nothing to install.
check_ad_policy 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_ad_policy 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_ad_policy. 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_ad_policy is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hermoso, and thousands of servers like it.
This server
Across the catalogue