Low Risk

meetlark_get_results

Get poll details and available time slots using a participation token. Returns the poll title, description, status, and time slots -- but NOT votes or participant data. This is the view a participant sees before voting. To see who voted and how, use meetlark_get_admin_view instead.

Part of the Meetlark MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call meetlark_get_results to retrieve information from Meetlark without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though meetlark_get_results only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

ai-meetlark-mcp-server.yaml
tools:
  meetlark_get_results:
    rules:
      - action: allow

See the full Meetlark policy for all 6 tools.

Tool Name meetlark_get_results
Category Read
MCP Server Meetlark MCP Server
Risk Level Low

Agents calling read-class tools like meetlark_get_results have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the meetlark_get_results tool do? +

Get poll details and available time slots using a participation token. Returns the poll title, description, status, and time slots -- but NOT votes or participant data. This is the view a participant sees before voting. To see who voted and how, use meetlark_get_admin_view instead.. It is categorised as a Read tool in the Meetlark MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on meetlark_get_results? +

Add a rule in your Intercept YAML policy under the tools section for meetlark_get_results. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Meetlark MCP server.

What risk level is meetlark_get_results? +

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

Can I rate-limit meetlark_get_results? +

Yes. Add a rate_limit block to the meetlark_get_results rule in your Intercept 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 meetlark_get_results completely? +

Set action: deny in the Intercept policy for meetlark_get_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.

What MCP server provides meetlark_get_results? +

meetlark_get_results is provided by the Meetlark MCP server (@meetlark/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Meetlark

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.