Clear all amber highlights in the Body panel. Does NOT touch what
AI agents use clear_body_highlights to create or update resources in MCPacer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCPacer environment.
The tool clears/removes UI highlights from the Body panel, which is a reversible modification of display state (highlights can be re-added). It does not delete underlying data, just resets a visual indicator. Classified as Write rather than Destructive because highlights can presumably be restored.
From the tool's definition Clear all amber highlights in the Body panel
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access clear_body_highlights gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCPacer, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_body_highlights:
{
"version": "1",
"default": "deny",
"tools": {
"clear_body_highlights": {
"limits": [
{
"counter": "clear_body_highlights_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}clear_body_highlights 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.
Clear all amber highlights in the Body panel. Does NOT touch what. It is categorised as a Write tool in the MCPacer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCPacer MCP server in PolicyLayer and add a rule for clear_body_highlights: 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 MCPacer. Nothing to install.
clear_body_highlights 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 clear_body_highlights 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 clear_body_highlights. 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.
clear_body_highlights is provided by the MCPacer MCP server (wernerpe/mcpacer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCPacer, 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.
32 MCPacer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.