strategy_vocabulary
AI agents call strategy_vocabulary to retrieve information from Polymarket BTC Backtester MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
With no description, confidence is reduced. However, the name and server context (backtesting/simulation) suggest this retrieves or queries metadata about available strategies or vocabulary—a read operation with no side effects. It does not modify data, execute external code, delete anything, or move money.
From the tool's definition Tool named 'strategy_vocabulary' on a backtesting server; no description provided. Based on context (sibling tools: backtest, data_coverage, get_price_series, list_markets, market_context), this appears to be a reference/lookup tool for available strategy…
Attacks that exploit this kind of access
strategy_vocabulary. It is categorised as a Read tool in the Polymarket BTC Backtester MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Polymarket BTC Backtester MCP Server MCP server in PolicyLayer and add a rule for strategy_vocabulary: 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 Polymarket BTC Backtester MCP Server. Nothing to install.
strategy_vocabulary 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 strategy_vocabulary 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 strategy_vocabulary. 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.
strategy_vocabulary is provided by the Polymarket BTC Backtester MCP Server MCP server (xin10ylop/polymarket-backtest-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 →