ftg_seller_catalog
Return seller catalogues registered on FTG — exporters and producers with their commodity, monthly capacity, certifications and target export markets. When to use this tool: an agent builds a supplier or sourcing shortlist. Input: optional seller country and commodity.
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/ftg-seller-catalog.md
What ftg_seller_catalog does on Mcp Knowledge
AI agents call ftg_seller_catalog to retrieve information from Mcp Knowledge 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 |
|---|---|---|---|
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
limit | integer | — | |
country | string | — | Optional seller country ISO code or name |
commodity | string | — | Optional commodity filter |
Parameters from the server's own tool schema.
Why ftg_seller_catalog is rated Low
The tool retrieves and returns existing catalog data about sellers/exporters. It queries the FTG database with optional filters (country, commodity) and returns information. There are no write, execute, or destructive side effects described.
From the tool's definition Return seller catalogues registered on FTG — exporters and producers with their commodity, monthly capacity, certifications and target export markets
Attacks that exploit this kind of access
The rule that runs ftg_seller_catalog safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ftg_seller_catalog, this is the rule to start with:
ftg_seller_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 Mcp Knowledge, apply this rule, and every ftg_seller_catalog call is checked against it from then on.
Questions about ftg_seller_catalog
Return seller catalogues registered on FTG — exporters and producers with their commodity, monthly capacity, certifications and target export markets. When to use this tool: an agent builds a supplier or sourcing shortlist. Input: optional seller country and commodity. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
ftg_seller_catalog accepts 4 parameters: async, limit, country, commodity. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for ftg_seller_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 Mcp Knowledge. Nothing to install.
ftg_seller_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 ftg_seller_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 ftg_seller_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.
ftg_seller_catalog is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue