generate_post_cover

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp

Medium RISK CLASS

Category Write

Parameters 83 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/generate-post-cover.md

WHAT IT DOES

What generate_post_cover does on FavCRM

AI agents use generate_post_cover to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.

Parameter	Type	Required	Description
`seed`	integer	—	Random seed for reproducible output
`postId`	string	Yes	The post ID
`prompt`	string	Yes	Image generation prompt
`modelCode`	string	Yes	Image model code from list_image_models (e.g. nano-banana-2)
`aspectRatio`	string	—	Aspect ratio passed to the model, e.g. "16:9", "1:1"
`pollTimeoutMs`	integer	—	Default 60000.
`negativePrompt`	string	—	Things to exclude from generation
`pollIntervalMs`	integer	—	Default 3000.

Parameters from the server's own tool schema.

RISK

Why generate_post_cover is rated Medium

This tool primarily creates new image assets and modifies post metadata (the featuredImage field and public URL), which are reversible write operations. While it incurs a financial cost (credits), the primary action is data modification rather than a financial transaction. The tool does not delete or irreversibly destroy data, does not execute arbitrary code, and does not move money directly.

From the tool's definition Tool description states it 'Generate[s] an AI image and attach[es] it as a post's featuredImage' and 'writes the public URL onto the post.' These are content creation and modification operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs generate_post_cover safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_post_cover, this is the rule to start with:

generate_post_cover Rate-limited

generate_post_cover 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_post_cover": {
      "limits": [
        {
          "counter": "generate_post_cover_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every generate_post_cover call is checked against it from then on.

FAQ

Questions about generate_post_cover

What does the generate_post_cover tool do? +

Generate an AI image and attach it as a post's featuredImage. Submits a kie.ai job, polls until complete, copies the result into the canonical post-asset R2 folder, and writes the public URL onto the post. Costs credits (see list_image_models). On poll timeout, the job continues — call attach_post_cover_from_job(postId, jobId) once it finishes to attach without paying again. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does generate_post_cover accept? +

generate_post_cover accepts 8 parameters: seed, postId, prompt, modelCode, aspectRatio, pollTimeoutMs, negativePrompt, pollIntervalMs. Required: postId, prompt, modelCode. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on generate_post_cover? +

Register the FavCRM MCP server in PolicyLayer and add a rule for generate_post_cover: 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 FavCRM. Nothing to install.

What risk level is generate_post_cover? +

generate_post_cover is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_post_cover? +

Yes. Add a rate_limit block to the generate_post_cover 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.

How do I block generate_post_cover completely? +

Set action: deny in the PolicyLayer policy for generate_post_cover. 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.

What MCP server provides generate_post_cover? +

generate_post_cover is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FavCRM, and thousands of servers like it.

This server

All 220 FavCRM tools →

Across the catalogue

generate_commit on MCP Server PR Pilot →generate_video_title on YouTube MCP Server →generate_devtools_report on Percepta MCP Server →generate_evidence_manifest on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →