Capture live traffic and check IPs against URLhaus blacklist
AI agents call check_threats to retrieve information from WireMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the sibling tool 'extract_credentials' in this server suggests potentially sensitive data access, 'check_threats' itself only queries and retrieves threat intelligence data without modifying systems, executing code, or causing irreversible changes.
From the tool's definition The tool 'check_threats' performs lookups: 'check IPs against URLhaus blacklist' implies querying an external threat database.
Documented attack patterns abuse exactly the kind of access check_threats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WireMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for check_threats:
{
"version": "1",
"default": "deny",
"tools": {
"check_threats": {}
}
}check_threats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Capture live traffic and check IPs against URLhaus blacklist. It is categorised as a Read tool in the WireMCP MCP Server, which means it retrieves data without modifying state.
Register the Wire MCP server in PolicyLayer and add a rule for check_threats: 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 WireMCP. Nothing to install.
check_threats 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_threats 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_threats. 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_threats is provided by the Wire MCP server (0xkoda/wiremcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 WireMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 WireMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.