List all Secureship API endpoints, optionally filtered by category. Categories include: carriers, shipment, history, address-book, auth, account, users, invoices, pickups, documents, integrations, settings, dashboard. Use for discovery when you don't know which endpoint to search for.
Part of the Multi-Carrier Shipping API — powered by Secureship MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call list_endpoints to retrieve information from Multi-Carrier Shipping API — powered by Secureship without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though list_endpoints only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
list_endpoints:
rules:
- action: allowSee the full Multi-Carrier Shipping API — powered by Secureship policy for all 4 tools.
Agents calling read-class tools like list_endpoints have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
List all Secureship API endpoints, optionally filtered by category. Categories include: carriers, shipment, history, address-book, auth, account, users, invoices, pickups, documents, integrations, settings, dashboard. Use for discovery when you don't know which endpoint to search for.. It is categorised as a Read tool in the Multi-Carrier Shipping API — powered by Secureship MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for list_endpoints. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Multi-Carrier Shipping API — powered by Secureship MCP server.
list_endpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_endpoints rule in your Intercept 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 Intercept policy for list_endpoints. 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.
list_endpoints is provided by the Multi-Carrier Shipping API — powered by Secureship MCP server (secureship/docs). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.