Enable or disable ad blocking
AI agents use unifi_set_ad_blocking to create or update resources in Multi-Tool MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Multi-Tool MCP Server environment.
This tool modifies UniFi controller configuration by toggling ad blocking settings. While reversible (can be toggled back), it changes system state and affects network behavior for all connected devices. It does not delete data (ruling out Destructive), execute arbitrary commands (ruling out Execute proper), or move money (ruling out Financial).
From the tool's definition The tool description states 'Enable or disable ad blocking', which modifies network controller settings on the UniFi system. This is a state-changing operation that affects network configuration.
Attacks that exploit this kind of access
Enable or disable ad blocking. It is categorised as a Write tool in the Multi-Tool MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Multi-Tool MCP Server MCP server in PolicyLayer and add a rule for unifi_set_ad_blocking: 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 Multi-Tool MCP Server. Nothing to install.
unifi_set_ad_blocking is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unifi_set_ad_blocking 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 unifi_set_ad_blocking. 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.
unifi_set_ad_blocking is provided by the Multi-Tool MCP Server MCP server (shawn-falconbury/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →