New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_reef_feed_by_wallet

Get reef posts by a specific wallet.

SERVERBasis MCP Server SOURCElaunch-on-basis/mcp-ts
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/launch-on-basis-mcp-ts/get-reef-feed-by-wallet.md

What get_reef_feed_by_wallet does on Basis MCP Server

AI agents call get_reef_feed_by_wallet 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_feed_by_wallet is rated Low

This tool retrieves or queries existing data (reef posts associated with a wallet) without creating, modifying, deleting, or executing any operations. It is a straightforward read-only query that returns information. Low severity because exposure of this tool poses minimal risk; an agent can only retrieve publicly or user-accessible post data without side effects.

From the tool's definition Tool name includes 'get_' prefix and description states 'Get reef posts by a specific wallet' — a retrieval operation with no modification or execution of transactions.

Questions about get_reef_feed_by_wallet

What does the get_reef_feed_by_wallet tool do? +

Get reef posts by a specific wallet. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_reef_feed_by_wallet? +

Register the Basis MCP Server MCP server in PolicyLayer and add a rule for get_reef_feed_by_wallet: 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 get_reef_feed_by_wallet? +

get_reef_feed_by_wallet is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_reef_feed_by_wallet? +

Yes. Add a rate_limit block to the get_reef_feed_by_wallet 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 get_reef_feed_by_wallet completely? +

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Basis MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.