generate_post · PostIdentity MCP Server MCP: Risk & Policy

WHAT IT DOES

What generate_post does on PostIdentity MCP Server

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

WHY IT NEEDS A POLICY

Why generate_post needs a policy

This tool creates new data (social media posts) that are posted to external platforms under claimed identities, which constitutes a Write operation. While reversible (posts can typically be deleted), the severity is medium rather than high because the primary risk is reputational/misinformation harm rather than system compromise.

From the tool's definition Tool 'generate_post' creates social media posts as specified by the user. Description states it 'Generate[s] a social media post' with cost implications, indicating persistent creation of content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_post Rate-limited

generate_post 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": {
      "limits": [
        {
          "counter": "generate_post_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches PostIdentity MCP Server, so you can run agents against it safely.

FAQ

Questions about generate_post

What does the generate_post tool do? +

Generate a social media post as one of your identities. Costs 1 credit per generation or refinement. It is categorised as a Write tool in the PostIdentity MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_post? +

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

What risk level is generate_post? +

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

Can I rate-limit generate_post? +

Yes. Add a rate_limit block to the generate_post 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 completely? +

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

generate_post is provided by the PostIdentity MCP Server MCP server (postidentity/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.