get_queue
Top UNCLAIMED posts in the owner's curated build order. Owner-ranked posts (queue_rank, lower = sooner) come first, then unranked planned posts by votes. Call this to find the next thing to build, then claim_post before starting work.
This record as markdown: /tools/com-featurejet-feedback-board/get-queue.md
What get_queue does on FeatureJet
AI agents call get_queue 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 | |
limit | object | — |
Parameters from the server's own tool schema.
Why get_queue is rated Low
This tool only reads and returns prioritized post data based on claim status and owner ranking. It has no capability to modify posts, delete them, execute code, or create financial obligations.
From the tool's definition Tool retrieves 'Top UNCLAIMED posts in the owner's curated build order' and description states 'Call this to find the next thing to build' — core function is querying/listing data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_queue 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 get_queue, this is the rule to start with:
get_queue 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 get_queue call is checked against it from then on.
Questions about get_queue
Top UNCLAIMED posts in the owner's curated build order. Owner-ranked posts (queue_rank, lower = sooner) come first, then unranked planned posts by votes. Call this to find the next thing to build, then claim_post before starting work. It is categorised as a Read tool in the FeatureJet MCP Server, which means it retrieves data without modifying state.
get_queue accepts 2 parameters: slug, limit. 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 get_queue: 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.
get_queue 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_queue 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_queue. 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_queue 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