Change an ADR
AI agents use adr_update_status to create or update resources in DevFlow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DevFlow MCP Server environment.
This tool creates or modifies data reversibly—updating an ADR's status is a write operation that can be undone (status can be changed again). It does not irreversibly delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or retrieve data without modification (Read).
From the tool's definition Tool name 'adr_update_status' and description 'Change an ADR' indicate modification of Architecture Decision Record status/state. ADRs are typically used for documenting architectural decisions in development workflows.
Attacks that exploit this kind of access
Change an ADR. It is categorised as a Write tool in the DevFlow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DevFlow MCP Server MCP server in PolicyLayer and add a rule for adr_update_status: 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.
adr_update_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the adr_update_status 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 adr_update_status. 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.
adr_update_status 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 →