AI agents use bluedart_import_waybill 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 waybills (shipping documents) in the BlueDart system, which is a write operation that generates new records. While reversible via the sibling bluedart_cancel_waybill tool, the creation itself is a modification operation.
From the tool's definition Tool description states "Create multiple BlueDart waybills in a single request via POST /waybill/v1/ImportData" — the verb "Create" combined with POST operation indicates data creation that modifies the shipping system state.
Attacks that exploit this kind of access
Create multiple BlueDart waybills in a single request via POST /waybill/v1/ImportData. 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_import_waybill: 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_import_waybill 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_import_waybill 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_import_waybill. 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_import_waybill 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 →