🚀 NEW: Smart context expansion. Get a function WITH its type definitions and immediate dependencies (signatures only). Saves 80-90% tokens vs reading all dependency files. Perfect for understanding code flow without full file reads.
AI agents call get_function_with_context to retrieve information from MCP Context Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs code navigation and retrieval operations with zero side effects. It queries and returns function definitions, type information, and dependency signatures—classic Read operations. The smart context expansion and token optimization do not change the fundamental operation: fetching code metadata for analysis. No data is modified, deleted, executed, or written back to the codebase.
From the tool's definition Tool retrieves function definitions and type information with dependencies (signatures only). Description emphasizes 'Get' and 'retrieval' operations with no mention of modification, deletion, or execution. Returns read-only code context data.
Documented attack patterns abuse exactly the kind of access get_function_with_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Context Manager, and nothing reaches the server without passing your rules. This is the rule we recommend for get_function_with_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_function_with_context": {}
}
}get_function_with_context 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.
🚀 NEW: Smart context expansion. Get a function WITH its type definitions and immediate dependencies (signatures only). Saves 80-90% tokens vs reading all dependency files. Perfect for understanding code flow without full file reads. It is categorised as a Read tool in the MCP Context Manager MCP Server, which means it retrieves data without modifying state.
Register the MCP Context Manager MCP server in PolicyLayer and add a rule for get_function_with_context: 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 MCP Context Manager. Nothing to install.
get_function_with_context 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 get_function_with_context 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 get_function_with_context. 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.
get_function_with_context is provided by the MCP Context Manager MCP server (transparentlyok/mcp-context-manager). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Context Manager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 MCP Context Manager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.