AI agents call get_post_upvoters 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 queries and returns existing data (list of upvoters) without modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius if misused—an agent could retrieve upvoter lists but cannot alter data or trigger external effects.
From the tool's definition Tool name 'get_post_upvoters' and description 'Get list of users who upvoted a post' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_post_upvoters 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_post_upvoters:
{
"version": "1",
"default": "deny",
"tools": {
"get_post_upvoters": {}
}
}get_post_upvoters 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.
Get list of users who upvoted a post. 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_post_upvoters: 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_post_upvoters 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_post_upvoters 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_post_upvoters. 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_post_upvoters 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.