// MCP TOOL REFERENCE

STEADYFETCH TOOLS

5 tools from the SteadyFetch MCP Server, categorised by risk level.

READ TOOLS

check_domain Check the health status of a domain. Returns the circuit breaker state: 'closed' (healthy), 'open' (failing), or 'half_open' (testing reco... fetch_markdown Fetch a URL and return clean markdown text optimized for LLM consumption. Same reliability as fetch_url but returns only the markdown content,... fetch_url Fetch a URL with full reliability — retry, circuit breaker, cache, and anti-bot bypass. Returns both raw HTML and clean markdown. Automaticall...

DESTRUCTIVE TOOLS

cache_stats Get cache statistics — size and item count. Useful for monitoring cache utilization and deciding when to clear. 4/5 clear_cache Clear the entire fetch cache. Use when you need fresh data and don't want to rely on cached results. 5/5

// FAQ

How many tools does the SteadyFetch MCP server have? +

The SteadyFetch MCP server exposes 5 tools across 2 categories: Read, Destructive.

How do I enforce policies on SteadyFetch tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the SteadyFetch server.

What risk categories do SteadyFetch tools fall into? +

SteadyFetch tools are categorised as Read (3), Destructive (2). Each category has a recommended default policy.

Enforce policies on SteadyFetch

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →