split_code

Split code into logical segments using AST analysis

SERVERContextForge MCP Gateway SOURCEjrmatherly/mcp-context-forge

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jrmatherly-mcp-context-forge/split-code.md

WHAT IT DOES

What split_code does on ContextForge MCP Gateway

AI agents call split_code to retrieve information from ContextForge MCP Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why split_code is rated Low

The tool performs static analysis of code via Abstract Syntax Tree (AST) traversal to segment and organize code logically. This is a read-only operation that retrieves structural information from code without mutation, execution, or destructive effects.

From the tool's definition Tool description states 'Split code into logical segments using AST analysis' — this is a parsing/analysis operation that examines code structure without modifying, executing, or deleting anything. No side effects are implied.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs split_code safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For split_code, this is the rule to start with:

split_code Allowed

split_code is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "split_code": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ContextForge MCP Gateway, apply this rule, and every split_code call is checked against it from then on.

FAQ

Questions about split_code

What does the split_code tool do? +

Split code into logical segments using AST analysis. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on split_code? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for split_code: 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 ContextForge MCP Gateway. Nothing to install.

What risk level is split_code? +

split_code is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit split_code? +

Yes. Add a rate_limit block to the split_code 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.

How do I block split_code completely? +

Set action: deny in the PolicyLayer policy for split_code. 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.

What MCP server provides split_code? +

split_code is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ContextForge MCP Gateway, and thousands of servers like it.

This server

All 221 ContextForge MCP Gateway tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →