get_cargo_catalog
Read the global Cargo catalog operating view: category and supplier counts, research runs, publication blockers, RFQ intakes, LP snapshots, and import batches. This catalog is independent of workspace Company records.
This record as markdown: /tools/sankahq-sanka-mcp/get-cargo-catalog.md
What get_cargo_catalog does on Sanka MCP Server
AI agents call get_cargo_catalog to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_cargo_catalog is rated Low
The tool retrieves and queries catalog information without side effects. The verb 'Read' in the description and the nature of the data returned (counts, snapshots, operational views) confirm this is a pure data retrieval operation. No creation, modification, execution, deletion, or financial impact is possible.
From the tool's definition Tool name 'get_cargo_catalog' and description 'Read the global Cargo catalog operating view' explicitly indicates a read-only operation that retrieves catalog metadata (category counts, supplier counts, research runs, publication blockers, RFQ intakes, LP…
Attacks that exploit this kind of access
The rule that runs get_cargo_catalog safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_cargo_catalog, this is the rule to start with:
get_cargo_catalog is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every get_cargo_catalog call is checked against it from then on.
Questions about get_cargo_catalog
Read the global Cargo catalog operating view: category and supplier counts, research runs, publication blockers, RFQ intakes, LP snapshots, and import batches. This catalog is independent of workspace Company records. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for get_cargo_catalog: 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 Sanka MCP Server. Nothing to install.
get_cargo_catalog 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 get_cargo_catalog 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 get_cargo_catalog. 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.
get_cargo_catalog is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue