List available OSINT tools in the catalog, optionally filtered by category.
AI agents call list_osint_tools to retrieve information from MCP OSINT Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs only informational queries against a tool catalog. It retrieves and returns data without creating, modifying, deleting, or executing anything. The optional filtering parameter allows structured queries but does not change state. The operation is idempotent and poses minimal security risk even if invoked by an AI agent without restrictions.
From the tool's definition Tool description states 'List available OSINT tools in the catalog, optionally filtered by category' — a pure retrieval operation with no side effects, no data modification, and no execution of external commands.
Attacks that exploit this kind of access
List available OSINT tools in the catalog, optionally filtered by category. It is categorised as a Read tool in the MCP OSINT Server MCP Server, which means it retrieves data without modifying state.
Register the MCP OSINT Server MCP server in PolicyLayer and add a rule for list_osint_tools: 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 MCP OSINT Server. Nothing to install.
list_osint_tools 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 list_osint_tools 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 list_osint_tools. 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.
list_osint_tools is provided by the MCP OSINT Server MCP server (lliwi/osint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →