AI agents call read_file_outline to retrieve information from Kontexta without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata (headings) from a markdown file without modifying, executing, or deleting anything. It is explicitly stated to be read-only with no side effects. The information returned is structural metadata (headings, line numbers, byte offsets) rather than sensitive data extraction. Misuse would be low-impact—an agent could only obtain outline information, not execute code or access restricted data.
From the tool's definition Tool name 'read_file_outline' and description 'Return a flat list of markdown headings for one file' and 'Read-only; no side effects'
Attacks that exploit this kind of access
Return a flat list of markdown headings for one file (level, text, line, byteStart, byteEnd). Read-only; no side effects, auth, or rate limits. Use as a cheap probe before. It is categorised as a Read tool in the Kontexta MCP Server, which means it retrieves data without modifying state.
Register the Kontexta MCP server in PolicyLayer and add a rule for read_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 Kontexta. Nothing to install.
read_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 read_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 read_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.
read_file_outline is provided by the Kontexta MCP server (safiyu/kontexta). 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 →