Suggest project tags for a piece of content using TF-IDF against the existing project tag pool. Never invents new tags — only existing ones are suggested, to avoid tag-wildwuchs. Use when you are writing a new doc-page / ADR / flow summary and want to tag it consistently with the rest of the proj...
AI agents call knowledge_autotag_suggest 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 analyzes existing content and tag metadata to recommend tags from a pre-existing pool. It performs statistical analysis (TF-IDF) on project data to return ranked suggestions with debugging information. There are no side effects, no data creation, modification, or deletion, and no external operations triggered.
From the tool's definition Tool description states it 'suggest[s] project tags' using TF-IDF analysis and 'Returns suggestions ranked by confidence' — a query/retrieval operation with no data modification, deletion, or external command execution.
Attacks that exploit this kind of access
Suggest project tags for a piece of content using TF-IDF against the existing project tag pool. Never invents new tags — only existing ones are suggested, to avoid tag-wildwuchs. Use when you are writing a new doc-page / ADR / flow summary and want to tag it consistently with the rest of the project. Returns suggestions ranked by confidence with matchedTokens for debuggability. Pass existingTags so already-applied tags are excluded from suggestions. 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 knowledge_autotag_suggest: 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.
knowledge_autotag_suggest 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 knowledge_autotag_suggest 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 knowledge_autotag_suggest. 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.
knowledge_autotag_suggest 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 →