Identify standard libraries, frameworks, and third-party code by analyzing imports and function names.
AI agents call detect_libraries to retrieve information from Kawaiidra MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs reconnaissance-style analysis (identifying and cataloging libraries and their imports) which is fundamentally a read-only operation. There are no side effects, no code execution, no data modification, and no destructive capabilities. Misuse would be limited to information gathering about a binary's composition, which poses minimal risk in the context of an AI agent's potential misuse.
From the tool's definition detect_libraries identifies standard libraries, frameworks, and third-party code by analyzing imports and function names—a query operation that performs static analysis without modifying the binary or invoking execution of code.
Documented attack patterns abuse exactly the kind of access detect_libraries gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kawaiidra MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for detect_libraries:
{
"version": "1",
"default": "deny",
"tools": {
"detect_libraries": {}
}
} detect_libraries 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.
Identify standard libraries, frameworks, and third-party code by analyzing imports and function names. It is categorised as a Read tool in the Kawaiidra MCP MCP Server, which means it retrieves data without modifying state.
Register the Kawaiidra MCP server in PolicyLayer and add a rule for detect_libraries: 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 Kawaiidra MCP. Nothing to install.
detect_libraries 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 detect_libraries 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 detect_libraries. 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.
detect_libraries is provided by the Kawaiidra MCP server (wagonbomb/kawaiidra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kawaiidra MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
94 Kawaiidra MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.