Upcoming vessel schedules. $0.02/call via x402 USDC.
Part of the Shipping Rates server.
Free to start. No card required.
AI agents use shippingrates_vessel_schedule to create or modify resources in Shipping Rates. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call shippingrates_vessel_schedule repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Shipping Rates.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"shippingrates_vessel_schedule": {
"limits": [
{
"counter": "shippingrates_vessel_schedule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Shipping Rates policy for all 19 tools.
These attack patterns abuse exactly the kind of access shippingrates_vessel_schedule gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Upcoming vessel schedules. $0.02/call via x402 USDC.. It is categorised as a Write tool in the Shipping Rates MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Shipping Rates MCP server in PolicyLayer and add a rule for shippingrates_vessel_schedule: 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 Shipping Rates. Nothing to install.
shippingrates_vessel_schedule 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 shippingrates_vessel_schedule 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 shippingrates_vessel_schedule. 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.
shippingrates_vessel_schedule is provided by the Shipping Rates MCP server (vinaybhosle/shippingrates-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Shipping Rates tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.