extract_classes

Extract class definitions from code

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/extract-classes.md

WHAT IT DOES

What extract_classes does on ContextForge MCP Gateway

AI agents call extract_classes 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 extract_classes is rated Low

This tool performs static code analysis to identify and return class definitions. It reads code input and produces informational output about code structure. There are no side effects, no code execution, no data modification, and no irreversible operations. It is a safe, non-destructive read operation.

From the tool's definition Tool name 'extract_classes' and description 'Extract class definitions from code' indicate a parsing/analysis operation that retrieves structural information from code without modifying, executing, or deleting anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs extract_classes 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 extract_classes, this is the rule to start with:

extract_classes Allowed

extract_classes 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": {
    "extract_classes": {}
  }
}

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 extract_classes call is checked against it from then on.

FAQ

Questions about extract_classes

What does the extract_classes tool do? +

Extract class definitions from code. 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 extract_classes? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for extract_classes: 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 extract_classes? +

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

Can I rate-limit extract_classes? +

Yes. Add a rate_limit block to the extract_classes 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 extract_classes completely? +

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

extract_classes 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 →