wayback_leaks

Wayback Leak Scan: Search Wayback Machine for historically exposed .env/config/secrets

SERVEROsint Terminal SOURCEhttps://osint-mcp.thetempleofdoom.com/mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-thetempleofdoom-osint-mcp-osint-terminal/wayback-leaks.md

WHAT IT DOES

What wayback_leaks does on Osint Terminal

AI agents call wayback_leaks 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.

RISK

Why wayback_leaks is rated Low

Even though wayback_leaks 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

RECOMMENDED RULE

The rule that runs wayback_leaks 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 wayback_leaks, this is the rule to start with:

wayback_leaks Allowed

wayback_leaks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wayback_leaks": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Osint Terminal, apply this rule, and every wayback_leaks call is checked against it from then on.

FAQ

Questions about wayback_leaks

What does the wayback_leaks tool do? +

Wayback Leak Scan: Search Wayback Machine for historically exposed .env/config/secrets. It is categorised as a Read tool in the Osint Terminal MCP Server, which means it retrieves data without modifying state.

What parameters does wayback_leaks accept? +

wayback_leaks accepts 1 parameter: q. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on wayback_leaks? +

Register the Osint Terminal MCP server in PolicyLayer and add a rule for wayback_leaks: 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.

What risk level is wayback_leaks? +

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

Can I rate-limit wayback_leaks? +

Yes. Add a rate_limit block to the wayback_leaks 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 wayback_leaks completely? +

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

wayback_leaks 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.

KEEP EXPLORING

More on Osint Terminal, and thousands of servers like it.

This server

All 474 Osint Terminal tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →