api_key_scan

API Key Exposure: Scan GitHub/Pastebin/Google for exposed API keys/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/api-key-scan.md

WHAT IT DOES

What api_key_scan does on Osint Terminal

AI agents call api_key_scan 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 api_key_scan is rated Low

Even though api_key_scan 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 api_key_scan 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 api_key_scan, this is the rule to start with:

api_key_scan Allowed

api_key_scan 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": {
    "api_key_scan": {}
  }
}

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 api_key_scan call is checked against it from then on.

FAQ

Questions about api_key_scan

What does the api_key_scan tool do? +

API Key Exposure: Scan GitHub/Pastebin/Google for exposed API keys/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 api_key_scan accept? +

api_key_scan 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 api_key_scan? +

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

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

Can I rate-limit api_key_scan? +

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

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

api_key_scan 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 →