# 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.

Agent View of the PolicyLayer registry record for `claim_post`. HTML page: https://policylayer.com/tools/com-featurejet-feedback-board/claim-post

## Facts

- Tool: `claim_post`
- Server: FeatureJet (`https://mcp.featurejet.com/mcp`) — https://policylayer.com/tools/com-featurejet-feedback-board.md
- Homepage: https://github.com/https://mcp.featurejet.com/mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 4 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `slug` | string | yes |  |
| `post_id` | integer | yes |  |
| `agent_label` | object | no |  |
| `ttl_seconds` | object | no |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "claim_post",
    "arguments": {
      "slug": "<slug>",
      "post_id": 0
    }
  }
}
```

## 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 own 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)."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches FeatureJet:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "claim_post": {
      "limits": [
        {
          "counter": "claim_post_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on FeatureJet (21)

- `delete_post` — Destructive — https://policylayer.com/tools/com-featurejet-feedback-board/delete-post.md
- `get_analytics` — Read — https://policylayer.com/tools/com-featurejet-feedback-board/get-analytics.md
- `get_board` — Read — https://policylayer.com/tools/com-featurejet-feedback-board/get-board.md
- `get_changelog` — Read — https://policylayer.com/tools/com-featurejet-feedback-board/get-changelog.md
- `get_post` — Read — https://policylayer.com/tools/com-featurejet-feedback-board/get-post.md
- `get_queue` — Read — https://policylayer.com/tools/com-featurejet-feedback-board/get-queue.md
- `list_boards` — Read — https://policylayer.com/tools/com-featurejet-feedback-board/list-boards.md
- `list_comments` — Read — https://policylayer.com/tools/com-featurejet-feedback-board/list-comments.md
- `list_posts` — Read — https://policylayer.com/tools/com-featurejet-feedback-board/list-posts.md
- `list_votes` — Read — https://policylayer.com/tools/com-featurejet-feedback-board/list-votes.md
- `ping` — Read — https://policylayer.com/tools/com-featurejet-feedback-board/ping.md
- `whoami` — Read — https://policylayer.com/tools/com-featurejet-feedback-board/whoami.md
- `add_evidence` — Write — https://policylayer.com/tools/com-featurejet-feedback-board/add-evidence.md
- `create_board` — Write — https://policylayer.com/tools/com-featurejet-feedback-board/create-board.md
- `create_comment` — Write — https://policylayer.com/tools/com-featurejet-feedback-board/create-comment.md
- `create_post` — Write — https://policylayer.com/tools/com-featurejet-feedback-board/create-post.md
- `propose_status` — Write — https://policylayer.com/tools/com-featurejet-feedback-board/propose-status.md
- `publish_board` — Write — https://policylayer.com/tools/com-featurejet-feedback-board/publish-board.md
- `release_post` — Write — https://policylayer.com/tools/com-featurejet-feedback-board/release-post.md
- `unpublish_board` — Write — https://policylayer.com/tools/com-featurejet-feedback-board/unpublish-board.md
- `update_post` — Write — https://policylayer.com/tools/com-featurejet-feedback-board/update-post.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-featurejet-feedback-board · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-featurejet-feedback-board