Edge-preserving bilateral filter.
AI agents use blur_bilateral to create or update resources in farshid-mcp-imageProcessing — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your farshid-mcp-imageProcessing environment.
A bilateral filter is an image processing operation that modifies image data by applying an edge-preserving blur. It reads an input image and writes/outputs a modified version. It does not delete data, execute code, or involve financial transactions. The modification is reversible since the original image can be retained. Severity is low as misuse is limited to producing a filtered image.
From the tool's definition bilateral filter
Attacks that exploit this kind of access
Edge-preserving bilateral filter. It is categorised as a Write tool in the farshid-mcp-imageProcessing MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the farshid-mcp-imageProcessing MCP server in PolicyLayer and add a rule for blur_bilateral: 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 farshid-mcp-imageProcessing. Nothing to install.
blur_bilateral 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 blur_bilateral 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 blur_bilateral. 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.
blur_bilateral is provided by the farshid-mcp-imageProcessing MCP server (pirahansiah/farshid-mcp-imageprocessing). 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 →