AI agents use animate_html to create or update resources in BWVI — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BWVI environment.
The tool modifies HTML by injecting CSS animations, which is a reversible write/modification operation. It doesn't execute arbitrary code, delete data, or have financial implications. The blast radius is medium since it alters design output but doesn't affect persistent data stores or system-level resources.
From the tool's definition "Inject CSS animations into HTML" — modifies existing HTML content by inserting CSS animation code
Documented attack patterns abuse exactly the kind of access animate_html gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BWVI, and nothing reaches the server without passing your rules. This is the rule we recommend for animate_html:
{
"version": "1",
"default": "deny",
"tools": {
"animate_html": {
"limits": [
{
"counter": "animate_html_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}animate_html stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Inject CSS animations into HTML. It is categorised as a Write tool in the BWVI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BWVI MCP server in PolicyLayer and add a rule for animate_html: 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 BWVI. Nothing to install.
animate_html 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 animate_html 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 animate_html. 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.
animate_html is provided by the BWVI MCP server (lh123aa/bwvi-design). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BWVI, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 BWVI tools catalogued and risk-classified — across an index of 43,000+ MCP servers.