Parse a source file from raw/ into structured code knowledge (AST, normalized model, summary). Currently supports COBOL (.cbl, .cob, .cpy). Persists artifacts under raw/parsed/cobol/. Optionally traces all references to a variable.
AI agents invoke code_parse to trigger actions in Agent Wiki. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool runs a parsing/analysis operation on source files and persists output artifacts to disk. This is more than a read — it executes a transformation pipeline (AST generation, normalization, summarization) and writes resulting files to storage. It does not delete or overwrite existing data irreversibly, so it falls under Execute (triggers external processing with side effects of file creation).
From the tool's definition 'Parse a source file... into structured code knowledge (AST, normalized model, summary)... Persists artifacts under raw/parsed/cobol/'
Attacks that exploit this kind of access
Parse a source file from raw/ into structured code knowledge (AST, normalized model, summary). Currently supports COBOL (.cbl, .cob, .cpy). Persists artifacts under raw/parsed/cobol/. Optionally traces all references to a variable. It is categorised as a Execute tool in the Agent Wiki MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Agent Wiki MCP server in PolicyLayer and add a rule for code_parse: 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 Agent Wiki. Nothing to install.
code_parse is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the code_parse 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 code_parse. 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.
code_parse is provided by the Agent Wiki MCP server (xinhuagu/agent-wiki). 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 →