Get comments for a post or changelog. Available fields: ${commentModel}, replies(${commentModel})
AI agents call get_comments to retrieve information from Featurebase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing comment data without creating, modifying, or deleting any records. It is a simple read operation on the Featurebase API, carrying minimal security risk since it does not alter state or execute arbitrary code. Risk is low even if misused by an agent, as the worst case is unauthorized viewing of comments.
From the tool's definition Tool name 'get_comments' and description 'Get comments for a post or changelog' indicate a retrieval operation with no modification or side effects. The specification of available fields (commentModel, replies) confirms a query-only function.
Documented attack patterns abuse exactly the kind of access get_comments 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 get_comments:
{
"version": "1",
"default": "deny",
"tools": {
"get_comments": {}
}
}get_comments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get comments for a post or changelog. Available fields: ${commentModel}, replies(${commentModel}). It is categorised as a Read tool in the Featurebase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Featurebase MCP Server MCP server in PolicyLayer and add a rule for get_comments: 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.
get_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_comments 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 get_comments. 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.
get_comments 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.