report_reef_post

Report a reef post.

SERVERBasis MCP Server SOURCElaunch-on-basis/mcp-ts

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/launch-on-basis-mcp-ts/report-reef-post.md

WHAT IT DOES

What report_reef_post does on Basis MCP Server

AI agents use report_reef_post to create or update resources in Basis MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Basis MCP Server environment.

RISK

Why report_reef_post is rated Medium

Reporting a post creates or modifies metadata/status associated with that post (marking it as reported), but does not permanently delete or destroy data. The action is reversible (a report can typically be withdrawn or cleared). This qualifies as Write rather than Destructive.

From the tool's definition 'Report a reef post' indicates modifying the state of a post by flagging or marking it with a report status, which is a reversible write operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs report_reef_post safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For report_reef_post, this is the rule to start with:

report_reef_post Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "report_reef_post": {
      "limits": [
        {
          "counter": "report_reef_post_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every report_reef_post call is checked against it from then on.

FAQ

Questions about report_reef_post

What does the report_reef_post tool do? +

Report a reef post. It is categorised as a Write tool in the Basis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on report_reef_post? +

Register the Basis MCP Server MCP server in PolicyLayer and add a rule for report_reef_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 Basis MCP Server. Nothing to install.

What risk level is report_reef_post? +

report_reef_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit report_reef_post? +

Yes. Add a rate_limit block to the report_reef_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.

How do I block report_reef_post completely? +

Set action: deny in the PolicyLayer policy for report_reef_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.

What MCP server provides report_reef_post? +

report_reef_post is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Basis MCP Server, and thousands of servers like it.

This server

All 204 Basis MCP Server tools →

Across the catalogue

generate_devtools_report on Percepta MCP Server →generate_forensic_report on Android Forensics ADB MCP Server →team_manager_post_blackboard on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →