This record as markdown: /tools/com-featurejet-feedback-board/list-comments.md
What list_comments does on FeatureJet
AI agents call list_comments to retrieve information from FeatureJet without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | |
post_id | integer | Yes |
Parameters from the server's own tool schema.
Why list_comments is rated Low
This tool queries and returns existing comments associated with a post. It performs a straightforward data retrieval operation without creating, modifying, deleting, or executing any actions. The use of 'list' in the name confirms it is a read-only operation. Blast radius is minimal—the only risk is potential information disclosure if sensitive comments exist, but the tool itself is not destructive or dangerous.
From the tool's definition Tool name 'list_comments' and description 'List comments for a post' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_comments safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureJet, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_comments, this is the rule to start with:
list_comments is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureJet, apply this rule, and every list_comments call is checked against it from then on.
Questions about list_comments
List comments for a post. It is categorised as a Read tool in the FeatureJet MCP Server, which means it retrieves data without modifying state.
list_comments accepts 2 parameters: slug, post_id. Required: slug, post_id. The full parameter table on this page comes from the server's own tool schema.
Register the FeatureJet MCP server in PolicyLayer and add a rule for list_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 FeatureJet. Nothing to install.
list_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 list_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 list_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.
list_comments is provided by the FeatureJet MCP server (https://mcp.featurejet.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureJet, and thousands of servers like it.
This server
Across the catalogue