Find posts similar to the given query text
AI agents call get_similar_submissions to retrieve information from Featurebase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data based on a search query, matching the Read category definition of 'retrieves or queries data; no side effects'. It does not create, modify, delete, execute code, or involve financial transactions. The confidence is high because the name and description clearly indicate read-only behavior with no side effects.
From the tool's definition Tool name 'get_similar_submissions' and description 'Find posts similar to the given query text' indicate a search/query operation that retrieves existing data without modification. The method performs a read-only similarity search against posts.
Documented attack patterns abuse exactly the kind of access get_similar_submissions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Featurebase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_similar_submissions:
{
"version": "1",
"default": "deny",
"tools": {
"get_similar_submissions": {}
}
}get_similar_submissions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find posts similar to the given query text. It is categorised as a Read tool in the Featurebase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Featurebase MCP Server MCP server in PolicyLayer and add a rule for get_similar_submissions: 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 Featurebase MCP Server. Nothing to install.
get_similar_submissions 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_similar_submissions 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_similar_submissions. 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_similar_submissions is provided by the Featurebase MCP Server MCP server (marcinwyszynski/featurebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Featurebase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Featurebase MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.