ftg_production_economics
Return production cost benchmarks (CAPEX/OPEX per unit, value ranges, scenarios, quality tiers) and agronomic yields (t/ha, cycles per year) for a commodity. When to use this tool: an agent sizes the economics of producing a commodity. Input: a commodity, with an optional country.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/ftg-production-economics.md
What ftg_production_economics does on Gapup Mcp
AI agents call ftg_production_economics to retrieve information from Gapup Mcp 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 country ISO code or name |
commodity | string | Yes | Commodity name or slug |
Parameters from the server's own tool schema.
Why ftg_production_economics is rated Low
This tool fetches and returns pre-existing reference data (cost benchmarks, yield statistics) for a given commodity and optional country. There are no side effects, no data modification, no execution of code, and no financial transactions. It is a straightforward data retrieval/query operation with low blast radius if misused.
From the tool's definition 'Return production cost benchmarks (CAPEX/OPEX per unit, value ranges, scenarios, quality tiers) and agronomic yields' — purely retrieves and returns benchmark data
Attacks that exploit this kind of access
The rule that runs ftg_production_economics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ftg_production_economics, this is the rule to start with:
ftg_production_economics 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 Gapup Mcp, apply this rule, and every ftg_production_economics call is checked against it from then on.
Questions about ftg_production_economics
Return production cost benchmarks (CAPEX/OPEX per unit, value ranges, scenarios, quality tiers) and agronomic yields (t/ha, cycles per year) for a commodity. When to use this tool: an agent sizes the economics of producing a commodity. Input: a commodity, with an optional country. It is categorised as a Read tool in the Gapup Mcp MCP Server, which means it retrieves data without modifying state.
ftg_production_economics accepts 4 parameters: async, limit, country, commodity. Required: commodity. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for ftg_production_economics: 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 Gapup Mcp. Nothing to install.
ftg_production_economics 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_production_economics 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_production_economics. 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_production_economics is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
This server
Across the catalogue