Pre-built codebase map — read before bulk file reads. Returns a compact outline derived from the tree-sitter call graph: per-file headlines with exports, signatures, token estimates, leading doc. Lets you answer
AI agents call chiasmus_map to retrieve information from Chiasmus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents static analysis metadata about code structure without modifying, executing, or deleting anything. It is fundamentally a query/analysis tool designed to help understand codebase organization before performing other operations. No arguments are mentioned that would allow execution of code or modification of data.
From the tool's definition Tool returns a read-only outline of codebase structure derived from call graph analysis: 'per-file headlines with exports, signatures, token estimates, leading doc.' The verb 'returns' and framing as a pre-built map indicate retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access chiasmus_map gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chiasmus, and nothing reaches the server without passing your rules. This is the rule we recommend for chiasmus_map:
{
"version": "1",
"default": "deny",
"tools": {
"chiasmus_map": {}
}
}chiasmus_map 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.
Pre-built codebase map — read before bulk file reads. Returns a compact outline derived from the tree-sitter call graph: per-file headlines with exports, signatures, token estimates, leading doc. Lets you answer. It is categorised as a Read tool in the Chiasmus MCP Server, which means it retrieves data without modifying state.
Register the Chiasmus MCP server in PolicyLayer and add a rule for chiasmus_map: 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 Chiasmus. Nothing to install.
chiasmus_map 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 chiasmus_map 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 chiasmus_map. 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.
chiasmus_map is provided by the Chiasmus MCP server (yogthos/chiasmus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Chiasmus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Chiasmus tools catalogued and risk-classified — across an index of 42,500+ MCP servers.