Low Risk

web_status

Check health status of all authenticated accounts. Shows cookie expiry, OAuth status, and issues.

How to control web_status ↓

What web_status does on Spectrawl

AI agents call web_status to retrieve information from Spectrawl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why web_status needs a policy

web_status retrieves and displays status information about authenticated accounts. It has no side effects: it does not modify credentials, delete accounts, execute commands, or trigger external actions. The blast radius of misuse is minimal — an agent with access to this tool could only learn metadata about account health, not compromise or alter accounts. This is a classic Read category tool.

From the tool's definition Tool description states it 'Check[s] health status' and 'Shows cookie expiry, OAuth status, and issues' — these are purely informational read operations with no modification, deletion, or execution capability.

Documented attack patterns abuse exactly the kind of access web_status gives an agent:

How to control web_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Spectrawl, and nothing reaches the server without passing your rules. This is the rule we recommend for web_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "web_status": {}
  }
}

web_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Spectrawl — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about web_status

What does the web_status tool do? +

Check health status of all authenticated accounts. Shows cookie expiry, OAuth status, and issues. It is categorised as a Read tool in the Spectrawl MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on web_status? +

Register the Spectrawl MCP server in PolicyLayer and add a rule for web_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 Spectrawl. Nothing to install.

What risk level is web_status? +

web_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit web_status? +

Yes. Add a rate_limit block to the web_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.

How do I block web_status completely? +

Set action: deny in the PolicyLayer policy for web_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.

What MCP server provides web_status? +

web_status is provided by the Spectrawl MCP server (pyx-corp/spectrawl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Spectrawl tool call.

Start from Spectrawl, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

5 Spectrawl tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.