claim_post
Atomically claim a post before working on it (double-work guard). ttl_seconds defaults to 3600 (max 86400); re-claiming with the same key extends the lease. Returns 409 if another key holds a live claim.
This record as markdown: /tools/com-featurejet-feedback-board/claim-post.md
What claim_post does on FeatureJet
AI agents use claim_post to create or update resources in FeatureJet, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureJet environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | |
post_id | integer | Yes | |
agent_label | object | — | |
ttl_seconds | object | — |
Parameters from the server's own tool schema.
Why claim_post is rated Medium
The tool modifies post state by establishing an exclusive claim or lease, which is a reversible write operation. It does not execute external code, delete data irreversibly, move funds, or merely read data. The medium severity reflects that incorrect claims could block legitimate work or cause coordination issues in a multi-agent system, but the effects are recoverable (lease expires or can be re-claimed).
From the tool's definition Tool description states it 'Atomically claim a post before working on it' and manages lease duration via 'ttl_seconds', indicating it modifies the state of a post (establishes a claim/lock).
Attacks that exploit this kind of access
The rule that runs claim_post 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 claim_post, this is the rule to start with:
claim_post 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.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureJet, apply this rule, and every claim_post call is checked against it from then on.
Questions about claim_post
Atomically claim a post before working on it (double-work guard). ttl_seconds defaults to 3600 (max 86400); re-claiming with the same key extends the lease. Returns 409 if another key holds a live claim. It is categorised as a Write tool in the FeatureJet MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
claim_post accepts 4 parameters: slug, post_id, agent_label, ttl_seconds. 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 claim_post: 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.
claim_post 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 claim_post 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 claim_post. 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.
claim_post 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