Create a new reef post.
AI agents use create_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.
This tool creates new user-generated content (a post) within the platform. It is a Write operation because it modifies the system state by adding new data. The severity is medium because misuse could result in spam, unwanted content, or reputational harm, but the impact is limited to one platform and reversible.
From the tool's definition 'Create a new reef post' is an action that generates new content/data in the Basis protocol system. The verb 'create' and the action of posting indicate data creation, which is reversible (posts can typically be deleted or edited).
Attacks that exploit this kind of access
Create a new 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.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_reef_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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →