shipper_receiver_counterparty_pack

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Medium RISK CLASS

Category Write

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/shipper-receiver-counterparty-pack.md

WHAT IT DOES

What shipper_receiver_counterparty_pack does on Livedatalink

AI agents use shipper_receiver_counterparty_pack to create or update resources in Livedatalink, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livedatalink environment.

Parameter	Type	Required	Description
`state`	string	—	Optional 2-letter state to disambiguate either party.
`format`	string	—	Report format. Defaults to markdown.
`shipper`	string	—	Shipper legal or trading name.
`receiver`	string	—	Receiver legal or trading name.

Parameters from the server's own tool schema.

RISK

Why shipper_receiver_counterparty_pack is rated Medium

An AI agent can call shipper_receiver_counterparty_pack faster than any human can review: one bad instruction and it creates or modifies resources in Livedatalink by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs shipper_receiver_counterparty_pack safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For shipper_receiver_counterparty_pack, this is the rule to start with:

shipper_receiver_counterparty_pack Rate-limited

shipper_receiver_counterparty_pack stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "shipper_receiver_counterparty_pack": {
      "limits": [
        {
          "counter": "shipper_receiver_counterparty_pack_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every shipper_receiver_counterparty_pack call is checked against it from then on.

FAQ

Questions about shipper_receiver_counterparty_pack

What does the shipper_receiver_counterparty_pack tool do? +

Create an evidence-backed counterparty pack for a shipper, receiver, or both. Resolves canonical identifiers, SEC/GLEIF/USAspending/EPA identity signals, sanctions status, and public-record standing, then returns a review checklist for credit terms and load release. Name matches are candidates to verify; this is not a credit report or endorsement. It is categorised as a Write tool in the Livedatalink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does shipper_receiver_counterparty_pack accept? +

shipper_receiver_counterparty_pack accepts 4 parameters: state, format, shipper, receiver. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on shipper_receiver_counterparty_pack? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for shipper_receiver_counterparty_pack: 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 Livedatalink. Nothing to install.

What risk level is shipper_receiver_counterparty_pack? +

shipper_receiver_counterparty_pack is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit shipper_receiver_counterparty_pack? +

Yes. Add a rate_limit block to the shipper_receiver_counterparty_pack 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.

How do I block shipper_receiver_counterparty_pack completely? +

Set action: deny in the PolicyLayer policy for shipper_receiver_counterparty_pack. 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.

What MCP server provides shipper_receiver_counterparty_pack? +

shipper_receiver_counterparty_pack is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 294 Livedatalink tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →