List KB articles for a help center; use published/draft/archived flags to filter lifecycle
AI agents call list_articles to retrieve information from SparrowDesk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists knowledge base articles with optional filtering by status. It has no side effects, does not create, modify, or delete data, and does not execute arbitrary operations. It is a straightforward read operation characteristic of data retrieval tools.
From the tool's definition Tool name 'list_articles' and description 'List KB articles for a help center; use published/draft/archived flags to filter lifecycle' indicate a query/retrieval operation with filtering parameters.
Attacks that exploit this kind of access
List KB articles for a help center; use published/draft/archived flags to filter lifecycle. It is categorised as a Read tool in the SparrowDesk MCP Server, which means it retrieves data without modifying state.
Register the SparrowDesk MCP server in PolicyLayer and add a rule for list_articles: 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.
list_articles 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 list_articles 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 list_articles. 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.
list_articles 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 →