Check the HTTP status and response time of one or more URLs.
AI agents call check_url_status to retrieve information from DevToolkit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs non-destructive information retrieval (HTTP HEAD or GET request to check status codes and measure response times). It has no side effects on the queried systems, creates no data modifications, executes no code, and poses minimal risk even if misused by an AI agent. Appropriate classification is Read.
From the tool's definition Tool description states 'Check the HTTP status and response time of one or more URLs' — a query operation that retrieves HTTP metadata without modifying or executing operations on the target systems.
Attacks that exploit this kind of access
Check the HTTP status and response time of one or more URLs. It is categorised as a Read tool in the DevToolkit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevToolkit MCP Server MCP server in PolicyLayer and add a rule for check_url_status: 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 DevToolkit MCP Server. Nothing to install.
check_url_status 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_status 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_status. 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_status is provided by the DevToolkit MCP Server MCP server (tusharrayamajhi/devtoolkit-mcp). 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 →