Upvote or downvote a tool within a WebMCP Hub config. Each user gets one vote per tool — voting the same direction again removes the vote. Use this to signal quality: upvote tools that work, downvote broken ones.
AI agents use contribute_vote-on-tool to create or update resources in MoltBrowser MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MoltBrowser MCP Server environment.
This tool creates or modifies data (vote records) in a reversible manner, fitting the Write category. It does not execute external operations, delete data permanently, move money, or read-only access—it specifically changes voting state. Severity is low because voting systems have minimal blast radius; erroneous votes can be easily corrected by toggling or re-voting.
From the tool's definition Tool description states it 'Upvote or downvote a tool' and 'voting the same direction again removes the vote', indicating modification of vote state data. The operation is reversible—votes can be added, toggled, or removed without permanent data loss.
Documented attack patterns abuse exactly the kind of access contribute_vote-on-tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MoltBrowser MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for contribute_vote-on-tool:
{
"version": "1",
"default": "deny",
"tools": {
"contribute_vote-on-tool": {
"limits": [
{
"counter": "contribute_vote-on-tool_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}contribute_vote-on-tool stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Upvote or downvote a tool within a WebMCP Hub config. Each user gets one vote per tool — voting the same direction again removes the vote. Use this to signal quality: upvote tools that work, downvote broken ones. It is categorised as a Write tool in the MoltBrowser MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MoltBrowser MCP Server MCP server in PolicyLayer and add a rule for contribute_vote-on-tool: 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 MoltBrowser MCP Server. Nothing to install.
contribute_vote-on-tool 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 contribute_vote-on-tool 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 contribute_vote-on-tool. 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.
contribute_vote-on-tool is provided by the MoltBrowser MCP Server MCP server (joakim-sael/moltbrowser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MoltBrowser 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.
9 MoltBrowser MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.