Search voting results from LegCo meetings
AI agents call search_voting_results to retrieve information from LegCo Search 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 historical voting data from a public legislative database. It performs no modifications, deletions, or external operations—purely information retrieval. The blast radius of misuse is minimal; an AI agent querying voting records poses no security, financial, or operational risk to the system or its users.
From the tool's definition Tool name 'search_voting_results' and description 'Search voting results from LegCo meetings' indicate a query/retrieval operation.
Attacks that exploit this kind of access
Search voting results from LegCo meetings. It is categorised as a Read tool in the LegCo Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LegCo Search MCP Server MCP server in PolicyLayer and add a rule for search_voting_results: 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 LegCo Search MCP Server. Nothing to install.
search_voting_results 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 search_voting_results 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 search_voting_results. 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.
search_voting_results is provided by the LegCo Search MCP Server MCP server (yellowcandle/legco-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →