get_pool_history

Get historical pool results. Shows past winners, price changes, pool sizes, and share distribution. Use this to calibrate your strategy.

SERVERConviction SOURCEabcxz/conviction-fm

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/abcxz-conviction-fm/get-pool-history.md

WHAT IT DOES

What get_pool_history does on Conviction

AI agents call get_pool_history to retrieve information from Conviction without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_pool_history is rated Low

The tool queries and retrieves historical information about competition pools. There are no side effects, no data modification, no financial transactions, and no code execution. This is clearly a Read operation with low severity since it only accesses historical data needed for strategy analysis.

From the tool's definition Tool description states it 'Shows past winners, price changes, pool sizes, and share distribution' and is used to 'calibrate your strategy.' These are all read operations that retrieve historical data without modifying state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_pool_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Conviction, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_pool_history, this is the rule to start with:

get_pool_history Allowed

get_pool_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_pool_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Conviction, apply this rule, and every get_pool_history call is checked against it from then on.

FAQ

Questions about get_pool_history

What does the get_pool_history tool do? +

Get historical pool results. Shows past winners, price changes, pool sizes, and share distribution. Use this to calibrate your strategy. It is categorised as a Read tool in the Conviction MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pool_history? +

Register the Conviction MCP server in PolicyLayer and add a rule for get_pool_history: 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 Conviction. Nothing to install.

What risk level is get_pool_history? +

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

Can I rate-limit get_pool_history? +

Yes. Add a rate_limit block to the get_pool_history 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.

How do I block get_pool_history completely? +

Set action: deny in the PolicyLayer policy for get_pool_history. 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 get_pool_history? +

get_pool_history is provided by the Conviction MCP server (abcxz/conviction-fm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Conviction, and thousands of servers like it.

This server

All 10 Conviction tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →