Archive a Knowledge Base article (hidden from the help center, not deleted)
AI agents use archive_article to create or update resources in SparrowDesk — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SparrowDesk environment.
Archiving is a write operation that modifies article visibility/status reversibly—archived articles can typically be unarchived. This is distinct from Destructive (which would be permanent deletion) and falls under Write category. Severity is medium because incorrect archiving of critical help center articles could impact customer support operations, but the action is reversible.
From the tool's definition Tool description states 'Archive a Knowledge Base article (hidden from the help center, not deleted)', indicating a reversible state change that hides content rather than permanently removing it.
Attacks that exploit this kind of access
Archive a Knowledge Base article (hidden from the help center, not deleted). It is categorised as a Write tool in the SparrowDesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SparrowDesk MCP server in PolicyLayer and add a rule for archive_article: 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 SparrowDesk. Nothing to install.
archive_article 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 archive_article 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 archive_article. 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.
archive_article is provided by the SparrowDesk MCP server (sparrowdesk/sparrowdesk-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 →