AI agents use create_post to create or update resources in Featurebase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Featurebase MCP Server environment.
This tool creates new feedback/feature request posts in Featurebase, which is a reversible write operation. It has no financial impact, does not execute arbitrary code, and does not delete data. The blast radius of misuse is limited to creating unwanted feedback posts that can be deleted or managed by admins. Low severity reflects that feedback post creation is a low-risk operation with minimal system impact.
From the tool's definition Tool name 'create_post' and description 'Create a new post' indicate data creation. Server context shows this manages 'feature requests, feedback posts, comments, and upvotes' through 'creating, updating, and organizing customer feedback.'
Documented attack patterns abuse exactly the kind of access create_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Featurebase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_post:
{
"version": "1",
"default": "deny",
"tools": {
"create_post": {
"limits": [
{
"counter": "create_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Free to start. No card required.
Create a new post. It is categorised as a Write tool in the Featurebase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Featurebase MCP Server MCP server in PolicyLayer and add a rule for create_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 Featurebase MCP Server. Nothing to install.
create_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_post is provided by the Featurebase MCP Server MCP server (marcinwyszynski/featurebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Featurebase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Featurebase MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.