Return the body of ONE heading (the heading line itself is excluded) plus level, line, size_bytes, and est_tokens. Heading match is case-insensitive but exact-string after trim — fuzzy / partial matches do NOT resolve. Returns isError if the heading is absent. Read-only; no side effects, auth, or...
AI agents call read_section 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 and queries data from a markdown knowledge vault without creating, modifying, deleting, or executing operations. The explicit 'Read-only' designation and absence of any state-changing actions place it squarely in the Read category with low severity, as misuse can only expose data already stored in the vault.
From the tool's definition Tool name 'read_section' and description states 'Return the body of ONE heading...Read-only; no side effects'. The description explicitly confirms read-only operation with no modifications or side effects.
Attacks that exploit this kind of access
Return the body of ONE heading (the heading line itself is excluded) plus level, line, size_bytes, and est_tokens. Heading match is case-insensitive but exact-string after trim — fuzzy / partial matches do NOT resolve. Returns isError if the heading is absent. Read-only; no side effects, auth, or rate limits. Pair with. 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_section: 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_section 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_section 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_section. 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_section 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 →