Check if a URL is safe and identify potential security risks
AI agents call check_url_safety to retrieve information from MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries URL safety information and returns analysis results. No data is created, modified, deleted, or executed. The tool has minimal blast radius even if misused—worst case, an agent performs unnecessary safety checks on URLs, which causes no harm.
From the tool's definition Tool performs URL safety checking and identifies security risks without modifying, executing, or deleting data. The verb 'check' and the purpose of identifying risks indicate a retrieval/analysis function with no side effects.
Attacks that exploit this kind of access
Check if a URL is safe and identify potential security risks. It is categorised as a Read tool in the MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the MCP-Server MCP server in PolicyLayer and add a rule for check_url_safety: 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 MCP-Server. Nothing to install.
check_url_safety 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 check_url_safety 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 check_url_safety. 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.
check_url_safety is provided by the MCP-Server MCP server (surbhimotghare/mcp-server). 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 →