list_posts
List posts for a board, optionally filtered by status, search, or tag.
This record as markdown: /tools/com-featurejet-feedback-board/list-posts.md
What list_posts does on FeatureJet
AI agents call list_posts 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 |
|---|---|---|---|
q | object | — | |
tag | object | — | |
slug | string | Yes | |
limit | object | — | |
offset | object | — | |
status | object | — |
Parameters from the server's own tool schema.
Why list_posts is rated Low
This tool retrieves and queries existing posts from a board with optional filtering parameters. It does not create, modify, delete, or execute any operations—it only returns data. This is a classic Read category operation with minimal risk if misused by an AI agent, as it cannot alter system state or cause harm through information retrieval alone.
From the tool's definition Tool name 'list_posts' and description 'List posts for a board, optionally filtered by status, search, or tag' indicate a retrieval operation with no side effects. The verb 'list' is explicitly a Read operation.
Attacks that exploit this kind of access
The rule that runs list_posts 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_posts, this is the rule to start with:
list_posts 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_posts call is checked against it from then on.
Questions about list_posts
List posts for a board, optionally filtered by status, search, or tag. It is categorised as a Read tool in the FeatureJet MCP Server, which means it retrieves data without modifying state.
list_posts accepts 6 parameters: q, tag, slug, limit, offset, status. Required: slug. 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_posts: 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_posts 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_posts 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_posts. 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_posts 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