sustainability_report
Rapport de durabilité — Gapup agent-payable C-suite expertise (SUSTAINABILITY). Returns a structured, audited deliverable. Reference case: GreenLoop Solutions — rapport durabilité B-Corp 2025 (95 FTE, €18M CA). Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/sustainability-report.md
What sustainability_report does on Gapup Mcp
AI agents use sustainability_report to commit financial operations through Gapup Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| 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 |
focus | string | — | |
company | object | Yes | |
pillars | object | Yes | |
stakeholders | array | Yes | |
targetLabels | array | — | |
existingLabels | array | — | |
audienceProfile | string | Yes |
Parameters from the server's own tool schema.
Why sustainability_report is rated Critical
The server explicitly states these are 'agent-payable tools' using x402 per-call micropayments. Each invocation of this tool incurs a financial charge, making it a Financial category tool.
From the tool's definition Gapup agent-payable ... x402 per-call; Returns a structured, audited deliverable; rapport durabilité B-Corp 2025
Risk signalsHigh parameter count (29 properties)
Attacks that exploit this kind of access
The rule that runs sustainability_report 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 sustainability_report, this is the rule to start with:
Any call to sustainability_report is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every sustainability_report call is checked against it from then on.
Questions about sustainability_report
Rapport de durabilité — Gapup agent-payable C-suite expertise (SUSTAINABILITY). Returns a structured, audited deliverable. Reference case: GreenLoop Solutions — rapport durabilité B-Corp 2025 (95 FTE, €18M CA). Inputs are validated server-side — send the documented case fields. It is categorised as a Financial tool in the Gapup Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
sustainability_report accepts 8 parameters: async, focus, company, pillars, stakeholders, targetLabels, existingLabels, audienceProfile. Required: company, pillars, stakeholders, audienceProfile. 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 sustainability_report: 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.
sustainability_report is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sustainability_report 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 sustainability_report. 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.
sustainability_report 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.
Across the catalogue