signallord_get_btc_metrics
AI agents call signallord_get_btc_metrics to retrieve information from Signallord without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Bitcoin market metrics and intelligence data with no side effects. Confidence is reduced to 0.7 rather than higher because the description is empty, leaving some ambiguity; however, the naming convention and sibling tool patterns strongly indicate it is a read-only data retrieval operation for financial market intelligence.
From the tool's definition Tool name 'signallord_get_btc_metrics' indicates data retrieval (get); all sibling tools on this server are read-only data queries (get_btc_gold_ratio, get_btc_vix_correlation, get_capitulation_score, get_composite_score, get_cycle_bottom_probability, etc.).
Attacks that exploit this kind of access
signallord_get_btc_metrics. It is categorised as a Read tool in the Signallord MCP Server, which means it retrieves data without modifying state.
Register the Signallord MCP server in PolicyLayer and add a rule for signallord_get_btc_metrics: 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 Signallord. Nothing to install.
signallord_get_btc_metrics 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 signallord_get_btc_metrics 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 signallord_get_btc_metrics. 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.
signallord_get_btc_metrics is provided by the Signallord MCP server (kk6bzb/signallord-mcp-server). 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 →