video_blur_region
Pixelates/blurs one or more rectangles over the video — the tool for redacting PII (an email pane, a name) before publishing a screen recording. Rects are in source pixels, top-left origin: [{x,y,w,h, start_ms?, end_ms?}] — omit the times to cover the whole clip. Great with a marker timeline's bo...
This record as markdown: /tools/com-local-mcp-local-mcp/video-blur-region.md
What video_blur_region does on Local
AI agents call video_blur_region to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
input | string | Yes | |
output | string | — | Default: <input>_blurred.mov |
regions | array | Yes | [{x,y,w,h, start_ms?, end_ms?}] in source pixels (top-left). |
Parameters from the server's own tool schema.
Why video_blur_region is rated Low
Even though video_blur_region only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs video_blur_region safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For video_blur_region, this is the rule to start with:
video_blur_region 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 Local, apply this rule, and every video_blur_region call is checked against it from then on.
Questions about video_blur_region
Pixelates/blurs one or more rectangles over the video — the tool for redacting PII (an email pane, a name) before publishing a screen recording. Rects are in source pixels, top-left origin: [{x,y,w,h, start_ms?, end_ms?}] — omit the times to cover the whole clip. Great with a marker timeline's bounds. Returns the output path. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
video_blur_region accepts 3 parameters: input, output, regions. Required: input, regions. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for video_blur_region: 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 Local. Nothing to install.
video_blur_region 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 video_blur_region 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 video_blur_region. 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.
video_blur_region is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue