Get processing status for a bulk contact creation job returned by bulk_create_contacts
AI agents call get_bulk_job_status 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 only retrieves information about an existing bulk job's processing status. It has no side effects, does not modify data, and does not trigger operations. It is a straightforward query operation that fits the Read category with low severity since status information disclosure carries minimal risk.
From the tool's definition The tool description states 'Get processing status' which is a retrieval operation. It queries the status of a bulk job without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get processing status for a bulk contact creation job returned by bulk_create_contacts. 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 get_bulk_job_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 SparrowDesk. Nothing to install.
get_bulk_job_status 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 get_bulk_job_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 get_bulk_job_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.
get_bulk_job_status 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 →