get_reef_post
Get a single reef post with comments.
This record as markdown: /tools/launch-on-basis-mcp-ts/get-reef-post.md
What get_reef_post does on Basis MCP Server
AI agents call get_reef_post 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.
Why get_reef_post is rated Low
This tool retrieves or queries a reef post and its associated comments without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation, consistent with the Read category.
From the tool's definition Tool name 'get_reef_post' and description 'Get a single reef post with comments' indicate retrieval of existing data with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs get_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 get_reef_post, this is the rule to start with:
get_reef_post is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every get_reef_post call is checked against it from then on.
Questions about get_reef_post
Get a single reef post with comments. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_reef_post is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.
More on Basis MCP Server, and thousands of servers like it.
This server
Across the catalogue