Return a compact context briefing for a flow: outgoing wiki links + backlinks + tags. Use this before writing a plan to pull relevant ADRs/Patterns automatically.
AI agents call wiki_get_flow_context to retrieve information from DevFlow 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 and contextual information about a flow without creating, modifying, deleting, or executing any actions. It functions as a read-only query to support planning, with no side effects or state changes.
From the tool's definition Tool name and description indicate retrieval operations only: 'Return a compact context briefing', 'pull relevant ADRs/Patterns' (fetch, no modification). Keywords 'get', 'outgoing wiki links', 'backlinks', 'tags' all suggest querying/retrieving existing data.
Attacks that exploit this kind of access
Return a compact context briefing for a flow: outgoing wiki links + backlinks + tags. Use this before writing a plan to pull relevant ADRs/Patterns automatically. It is categorised as a Read tool in the DevFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevFlow MCP Server MCP server in PolicyLayer and add a rule for wiki_get_flow_context: 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 DevFlow MCP Server. Nothing to install.
wiki_get_flow_context 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 wiki_get_flow_context 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 wiki_get_flow_context. 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.
wiki_get_flow_context is provided by the DevFlow MCP Server MCP server (klausfreiberufler/devflow-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 →