lane_location_risk_pack

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 72 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/lane-location-risk-pack.md

WHAT IT DOES

What lane_location_risk_pack does on Livedatalink

AI agents call lane_location_risk_pack to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`format`	string	—	Report format. Defaults to markdown.
`origin_area`	string	—	Optional origin county/place for FEMA history.
`origin_state`	string	—	Optional origin 2-letter state, required with origin_area.
`origin_address`	string	Yes	Full US origin street address.
`destination_area`	string	—	Optional destination county/place for FEMA history.
`destination_state`	string	—	Optional destination 2-letter state, required with destination_area.
`destination_address`	string	Yes	Full US destination street address.

Parameters from the server's own tool schema.

RISK

Why lane_location_risk_pack is rated Low

Even though lane_location_risk_pack only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lane_location_risk_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 lane_location_risk_pack, this is the rule to start with:

lane_location_risk_pack Allowed

lane_location_risk_pack is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lane_location_risk_pack": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about lane_location_risk_pack

What does the lane_location_risk_pack tool do? +

Compare origin and destination risk for a logistics lane. Runs site-bound hazard/environmental profiles for both addresses and optionally adds FEMA disaster history for each area. Returns source coverage, point-in-time risk evidence, and an operational review checklist. This is informational public-record synthesis, not an insurance rating or route guarantee. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does lane_location_risk_pack accept? +

lane_location_risk_pack accepts 7 parameters: format, origin_area, origin_state, origin_address, destination_area, destination_state, destination_address. Required: origin_address, destination_address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on lane_location_risk_pack? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for lane_location_risk_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 lane_location_risk_pack? +

lane_location_risk_pack is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit lane_location_risk_pack? +

Yes. Add a rate_limit block to the lane_location_risk_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 lane_location_risk_pack completely? +

Set action: deny in the PolicyLayer policy for lane_location_risk_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 lane_location_risk_pack? +

lane_location_risk_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

aiva_get_churn_risk on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →