Find cryptographic constants like AES S-boxes, CRC tables, and magic numbers. Useful for identifying crypto implementations.
AI agents call find_crypto_constants 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 static binary analysis to locate and identify cryptographic constants within a binary. It retrieves information from an already-loaded binary artifact (via Ghidra) without modifying the binary, executing arbitrary code, or triggering side effects. The operation is purely informational/read-only, analogous to a search or grep operation.
From the tool's definition Tool description states it "Find[s] cryptographic constants" and "identify[ing] crypto implementations" — a passive search and analysis operation with no modification, deletion, or execution of external code.
Documented attack patterns abuse exactly the kind of access find_crypto_constants 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 find_crypto_constants:
{
"version": "1",
"default": "deny",
"tools": {
"find_crypto_constants": {}
}
} find_crypto_constants 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.
Find cryptographic constants like AES S-boxes, CRC tables, and magic numbers. Useful for identifying crypto implementations. 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 find_crypto_constants: 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.
find_crypto_constants 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 find_crypto_constants 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 find_crypto_constants. 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.
find_crypto_constants 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.