AI agents use create_comment 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.
Creating comments is a reversible write operation that adds new data to the system. It modifies the feedback/comment structure but does not execute arbitrary code, delete data, or involve financial transactions. The severity is medium because widespread comment creation could spam the system or mislead users, but individual comments can be deleted and the impact is contained to the Featurebase platform.
From the tool's definition Tool name 'create_comment' and description 'Create a new comment or reply' indicate creation of new data. Sibling tools include 'delete_comment' and 'delete_post', confirming this server manages mutable feedback data.
Documented attack patterns abuse exactly the kind of access create_comment 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_comment:
{
"version": "1",
"default": "deny",
"tools": {
"create_comment": {
"limits": [
{
"counter": "create_comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_comment 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 comment or reply. 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_comment: 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_comment 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_comment 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_comment. 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_comment 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.