fetch tool reference for StifLi Flex MCP
Sensitive readfetches a URL using the WordPress HTTP API. It supports method, query params, headers, timeout, redirects, HEAD mode, text extraction, and byte limits.
Description
fetches a URL using the WordPress HTTP API. It supports method, query params, headers, timeout, redirects, HEAD mode, text extraction, and byte limits.
What it is for
- Querying external APIs.
- Checking a URL or reading remote content.
Example use case
checking an external endpoint.
Sample prompt
Fetch the headers for this public API endpoint and tell me whether it responds successfully.
Sample response
{
"tool": "fetch",
"status": "ok",
"items": []
}
What does fetch do?
fetches a URL using the WordPress HTTP API. It supports method, query params, headers, timeout, redirects, HEAD mode, text extraction, and byte limits.
Does fetch modify site data?
It does not modify data, but it can expose sensitive site, user, or configuration details.
Which capability is commonly required?
It usually runs under controls compatible with profile-enabled access and the active MCP profile.
How should fetch be used safely?
Restrict this tool by profile and avoid exposing full raw output in shared channels.