httpstatus
HTTP Status: Explain an HTTP status code (offline)
This record as markdown: /tools/com-thetempleofdoom-osint-mcp-osint-terminal/httpstatus.md
What httpstatus does on Osint Terminal
AI agents call httpstatus to retrieve information from Osint Terminal without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | — |
Parameters from the server's own tool schema.
Why httpstatus is rated Low
Even though httpstatus only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs httpstatus safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Osint Terminal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For httpstatus, this is the rule to start with:
httpstatus is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Osint Terminal, apply this rule, and every httpstatus call is checked against it from then on.
Questions about httpstatus
HTTP Status: Explain an HTTP status code (offline). It is categorised as a Read tool in the Osint Terminal MCP Server, which means it retrieves data without modifying state.
httpstatus accepts 1 parameter: q. The full parameter table on this page comes from the server's own tool schema.
Register the Osint Terminal MCP server in PolicyLayer and add a rule for httpstatus: 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 Osint Terminal. Nothing to install.
httpstatus 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 httpstatus 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 httpstatus. 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.
httpstatus is provided by the Osint Terminal MCP server (https://osint-mcp.thetempleofdoom.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Osint Terminal, and thousands of servers like it.
This server
Across the catalogue