Retrieve metadata for a specific function by its fully qualified name.
AI agents call get_function_metadata to retrieve information from CodeFlow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool extracts function metadata (likely signatures, documentation, parameters, return types) from an analyzed codebase. It performs a pure query operation on existing code analysis data without modifying, deleting, or executing anything. The blast radius of misuse is minimal—an agent could retrieve unwanted metadata but cannot alter code, execute operations, or cause destructive effects.
From the tool's definition Tool name 'get_function_metadata' and description 'Retrieve metadata for a specific function' indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Retrieve metadata for a specific function by its fully qualified name. It is categorised as a Read tool in the CodeFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CodeFlow MCP Server MCP server in PolicyLayer and add a rule for get_function_metadata: 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 CodeFlow MCP Server. Nothing to install.
get_function_metadata 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_metadata 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_metadata. 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_metadata is provided by the CodeFlow MCP Server MCP server (mrorigo/code-flow-mcp). 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 →