Get metadata about the current Contextflow snapshot: repository name, branch, number of indexed files and vectorized chunks, and its processing status.
AI agents call get_context_info to retrieve information from Contextflow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves informational metadata about a repository snapshot without querying, modifying, or executing any code. It is purely a metadata inspection utility with no destructive, write, or execution capabilities. The low severity reflects minimal risk from misuse—returning repository statistics poses no security threat.
From the tool's definition Tool description states it 'Get[s] metadata about the current Contextflow snapshot: repository name, branch, number of indexed files and vectorized chunks, and its processing status.' The verbs 'get' and the focus on retrieving metadata with no side effects…
Attacks that exploit this kind of access
Get metadata about the current Contextflow snapshot: repository name, branch, number of indexed files and vectorized chunks, and its processing status. It is categorised as a Read tool in the Contextflow MCP Server, which means it retrieves data without modifying state.
Register the Contextflow MCP server in PolicyLayer and add a rule for get_context_info: 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 Contextflow. Nothing to install.
get_context_info 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_context_info 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_context_info. 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_context_info is provided by the Contextflow MCP server (millermarru/mcpcontext). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_context_info is one line of Contextflow's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →