# get_reef_highlights

Get highlighted reef posts.

Agent View of the PolicyLayer registry record for `get_reef_highlights`. HTML page: https://policylayer.com/tools/launch-on-basis-mcp-ts/get-reef-highlights

## Facts

- Tool: `get_reef_highlights`
- Server: Basis MCP Server (`launch-on-basis/mcp-ts`) — https://policylayer.com/tools/launch-on-basis-mcp-ts.md
- Homepage: https://github.com/Launch-On-Basis/MCP-TS
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_reef_highlights",
    "arguments": {}
  }
}
```

## Why get_reef_highlights is rated Low

This tool queries and retrieves data (highlighted reef posts) without modifying, creating, or deleting any information. It performs a simple read operation with no capability to alter state or trigger external actions. The low severity reflects the minimal risk if misused by an AI agent—at worst, it retrieves unwanted information.

From the tool's own definition: "Tool name 'get_reef_highlights' and description 'Get highlighted reef posts' indicate a retrieval operation with no side effects."

## Use case

AI agents call get_reef_highlights to retrieve information from Basis MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Basis MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_reef_highlights": {}
  }
}
```

## Other tools on Basis MCP Server (203)

- `cancel_order` — Destructive — https://policylayer.com/tools/launch-on-basis-mcp-ts/cancel-order.md
- `delete_project_comment` — Destructive — https://policylayer.com/tools/launch-on-basis-mcp-ts/delete-project-comment.md
- `delete_reef_comment` — Destructive — https://policylayer.com/tools/launch-on-basis-mcp-ts/delete-reef-comment.md
- `delete_reef_post` — Destructive — https://policylayer.com/tools/launch-on-basis-mcp-ts/delete-reef-post.md
- `pm_cancel_order` — Destructive — https://policylayer.com/tools/launch-on-basis-mcp-ts/pm-cancel-order.md
- `remove_dev_share` — Destructive — https://policylayer.com/tools/launch-on-basis-mcp-ts/remove-dev-share.md
- `unfreeze_token` — Destructive — https://policylayer.com/tools/launch-on-basis-mcp-ts/unfreeze-token.md
- `link_moltbook` — Execute — https://policylayer.com/tools/launch-on-basis-mcp-ts/link-moltbook.md
- `start_surge_tax` — Execute — https://policylayer.com/tools/launch-on-basis-mcp-ts/start-surge-tax.md
- `sync_order` — Execute — https://policylayer.com/tools/launch-on-basis-mcp-ts/sync-order.md
- `updown_cancel_stalled` — Execute — https://policylayer.com/tools/launch-on-basis-mcp-ts/updown-cancel-stalled.md
- `veto_outcome` — Execute — https://policylayer.com/tools/launch-on-basis-mcp-ts/veto-outcome.md
- `vote_on_dispute` — Execute — https://policylayer.com/tools/launch-on-basis-mcp-ts/vote-on-dispute.md
- `bet` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/bet.md
- `buy_multiple_orders` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/buy-multiple-orders.md
- `buy_order` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/buy-order.md
- `buy_orders_and_contract` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/buy-orders-and-contract.md
- `buy_token` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/buy-token.md
- `claim_bounty` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/claim-bounty.md
- `claim_faucet` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/claim-faucet.md
- `claim_leverage_liquidation` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/claim-leverage-liquidation.md
- `close_leverage` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/close-leverage.md
- `dispute_outcome` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/dispute-outcome.md
- `finalize_market` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/finalize-market.md
- `leverage_buy` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/leverage-buy.md
- `pm_buy` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/pm-buy.md
- `pm_buy_multiple_orders` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/pm-buy-multiple-orders.md
- `pm_buy_order` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/pm-buy-order.md
- `pm_buy_orders_and_contract` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/pm-buy-orders-and-contract.md
- `pm_finalize` — Financial — https://policylayer.com/tools/launch-on-basis-mcp-ts/pm-finalize.md
- …and 173 more: https://policylayer.com/tools/launch-on-basis-mcp-ts.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=launch-on-basis-mcp-ts · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/launch-on-basis-mcp-ts