import_cargo_catalog
Idempotently import a normalized Cargo research bundle into the global catalog. The bundle may contain categories, suppliers, research runs, sources, claims, raw artifacts, and draft or ready-for-review LP snapshots. This tool never publishes an LP snapshot.
This record as markdown: /tools/sankahq-sanka-mcp/import-cargo-catalog.md
What import_cargo_catalog does on Sanka MCP Server
AI agents use import_cargo_catalog to create or update resources in Sanka MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.
Why import_cargo_catalog is rated Medium
This tool creates or modifies multiple types of records in a catalog system (categories, suppliers, research runs, sources, claims, artifacts, snapshots). Although 'import' could suggest a read operation, the functional effect is to populate or update the global catalog with new data structures. The tool is idempotent (safe to repeat) and explicitly does not publish, suggesting the changes are not final/destructive.
From the tool's definition The tool performs 'import' operations that create or modify data ('categories, suppliers, research runs, sources, claims, raw artifacts, and draft or ready-for-review LP snapshots').
Attacks that exploit this kind of access
The rule that runs import_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 import_cargo_catalog, this is the rule to start with:
import_cargo_catalog 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every import_cargo_catalog call is checked against it from then on.
Questions about import_cargo_catalog
Idempotently import a normalized Cargo research bundle into the global catalog. The bundle may contain categories, suppliers, research runs, sources, claims, raw artifacts, and draft or ready-for-review LP snapshots. This tool never publishes an LP snapshot. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for import_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.
import_cargo_catalog 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 import_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 import_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.
import_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