Raw votes from all 12 oracle signals with per-signal confidence and consensus score. Each oracle is a separate real-world data source: funding rate, open interest, long/short ratio, Fear & Greed index, macro regime (FRED), aviation volume, TSA travel demand, Polymarket crowd, options flow, congre...
Risk signalsHandles credentials or secrets (api_key)
Part of the Octodamus Intelligence Oracle server.
Free to start. No card required.
AI agents call get_oracle_signals to retrieve information from Octodamus Intelligence Oracle 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 get_oracle_signals 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.
{
"version": "1",
"default": "deny",
"tools": {
"get_oracle_signals": {}
}
}See the full Octodamus Intelligence Oracle policy for all 10 tools.
These attack patterns abuse exactly the kind of access get_oracle_signals gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Raw votes from all 12 oracle signals with per-signal confidence and consensus score. Each oracle is a separate real-world data source: funding rate, open interest, long/short ratio, Fear & Greed index, macro regime (FRED), aviation volume, TSA travel demand, Polymarket crowd, options flow, congressional trading, CLOB order book depth, and Binance 24h cumulative delta. Each votes BUY (+1), SELL (-1), or NEUTRAL (0) independently. Use this for deep analysis, signal attribution, or debugging a BUY/SELL/HOLD decision. For a consolidated action, call get_agent_signal() instead. Response example: { "consensus_score": 8, "max_score": 12, "action": "BUY", "win_rate": 0.62, "oracles": [ {"name": "funding_rate", "vote": 1, "confidence": 0.85}, {"name": "long_short_ratio", "vote": 1, "confidence": 0.70}, {"name": "fear_greed", "vote": 0, "confidence": 0.50}, {"name": "macro_regime", "vote": 1, "confidence": 0.80}, {"name": "binance_delta", "vote": 1, "confidence": 0.75} ] }. It is categorised as a Read tool in the Octodamus Intelligence Oracle MCP Server, which means it retrieves data without modifying state.
Register the Octodamus Intelligence Oracle MCP server in PolicyLayer and add a rule for get_oracle_signals: 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 Octodamus Intelligence Oracle. Nothing to install.
get_oracle_signals 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 get_oracle_signals 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 get_oracle_signals. 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.
get_oracle_signals is provided by the Octodamus Intelligence Oracle MCP server (https://api.octodamus.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Octodamus Intelligence Oracle tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.