extract_functions

Extract function 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-functions.md

WHAT IT DOES

What extract_functions does on ContextForge MCP Gateway

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

This tool performs static analysis to extract and return function definitions from provided code. It retrieves information without side effects, modification, or execution of the code being analyzed. The action is read-only analysis, making it a Read category tool with low severity.

From the tool's definition Tool name is 'extract_functions' and description states 'Extract function definitions from code' — a retrieval/analysis operation with no modification, execution, or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

extract_functions Allowed

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

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

FAQ

Questions about extract_functions

What does the extract_functions tool do? +

Extract function 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_functions? +

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

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

Can I rate-limit extract_functions? +

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

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

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