Get a structural outline of a source file from: ${resolvedSourcePath}. Extracts function names, class definitions, and other important symbols. Useful for understanding file structure without reading entire contents.
AI agents call get_file_outline to retrieve information from Cross-Project MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about code structure (outline, symbols, definitions) from an existing source file without modifying, executing, or deleting anything. It is purely informational and read-only, making it a Read category tool with low severity since misuse would only expose code structure information, not sensitive data or enable execution.
From the tool's definition Tool description states it 'Extracts function names, class definitions, and other important symbols' and is 'Useful for understanding file structure without reading entire contents.' The verb 'Get' and the read-only nature of extracting structural metadata…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get a structural outline of a source file from: ${resolvedSourcePath}. Extracts function names, class definitions, and other important symbols. Useful for understanding file structure without reading entire contents. It is categorised as a Read tool in the Cross-Project MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cross-Project MCP Server MCP server in PolicyLayer and add a rule for get_file_outline: 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 Cross-Project MCP Server. Nothing to install.
get_file_outline 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_file_outline 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_file_outline. 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_file_outline is provided by the Cross-Project MCP Server MCP server (sweetsrepo/cross-project-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 →