List Knowledge Base help centers for the account (needed for helpCenterId on articles/collections)
AI agents call list_helpcenters 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 existing help centers without creating, modifying, deleting, or executing anything. It is a pure read operation with minimal blast radius—an AI agent misusing it would only see help center information already accessible to the account.
From the tool's definition Tool name 'list_helpcenters' and description 'List Knowledge Base help centers' indicate a retrieval operation with no side effects. The purpose is to query and return existing help center data needed for reference in other operations.
Attacks that exploit this kind of access
List Knowledge Base help centers for the account (needed for helpCenterId on articles/collections). 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_helpcenters: 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_helpcenters 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_helpcenters 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_helpcenters. 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_helpcenters 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 →