Hough circle detection.
AI agents call detect_circles to retrieve information from farshid-mcp-imageProcessing without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is an image analysis/detection tool that processes visual data to extract information (circle locations, radii, confidence) without creating side effects, modifying data irreversibly, executing arbitrary code, or moving resources. It falls squarely into the Read category alongside the sibling detect_faces, detect_eyes, and detect_corners tools.
From the tool's definition Tool performs circle detection using Hough transform on images—a computer vision analysis operation that identifies geometric shapes.
Attacks that exploit this kind of access
Hough circle detection. It is categorised as a Read tool in the farshid-mcp-imageProcessing MCP Server, which means it retrieves data without modifying state.
Register the farshid-mcp-imageProcessing MCP server in PolicyLayer and add a rule for detect_circles: 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.
detect_circles 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 detect_circles 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 detect_circles. 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.
detect_circles 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 →