content_engine
Moteur de contenu — Gapup agent-payable C-suite expertise (CMO). Returns a structured, audited deliverable. Reference case: Notion — content engine 2026 (productivity B2B). Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/content-engine.md
What content_engine does on Gapup Mcp
AI agents use content_engine 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 |
brand | object | Yes | |
months | integer | Yes | |
cluster | object | Yes | |
maxArticlesPerMonth | integer | Yes |
Parameters from the server's own tool schema.
Why content_engine is rated Critical
The server explicitly states '271 agent-payable tools' and 'x402 per-call', meaning every call to content_engine incurs a financial charge. While the tool's functional output is a content/marketing deliverable (Write/Read category), the payment obligation triggered on each call makes Financial the most severe applicable category.
From the tool's definition Gapup agent-payable ... x402 per-call — each invocation triggers a payment transaction under the x402 micropayment protocol
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs content_engine 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 content_engine, this is the rule to start with:
Any call to content_engine 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 content_engine call is checked against it from then on.
Questions about content_engine
Moteur de contenu — Gapup agent-payable C-suite expertise (CMO). Returns a structured, audited deliverable. Reference case: Notion — content engine 2026 (productivity B2B). 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.
content_engine accepts 5 parameters: async, brand, months, cluster, maxArticlesPerMonth. Required: brand, months, cluster, maxArticlesPerMonth. 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 content_engine: 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.
content_engine 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 content_engine 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 content_engine. 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.
content_engine 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