AI agents use bluedart_register_pickup to create or update resources in Bluedart — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bluedart environment.
This tool creates a new pickup record in BlueDart's system, reversibly registering a scheduled pickup at a customer location. It is a Write operation (creates/registers data) rather than Execute (no command execution) or Destructive (the operation is reversible—pickups can be cancelled via the sibling bluedart_cancel_pickup tool).
From the tool's definition The tool description states it uses POST /pickup/v1/RegisterPickup, which schedules a pickup—a create operation that modifies BlueDart's system state by adding a new pickup appointment.
Attacks that exploit this kind of access
Schedule a BlueDart pickup at the customer location via POST /pickup/v1/RegisterPickup. It is categorised as a Write tool in the Bluedart MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bluedart MCP server in PolicyLayer and add a rule for bluedart_register_pickup: 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 Bluedart. Nothing to install.
bluedart_register_pickup 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 bluedart_register_pickup 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 bluedart_register_pickup. 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.
bluedart_register_pickup is provided by the Bluedart MCP server (nidhiyashwanth/bluedart-mcp-server). 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 →