signallord_get_etf_flow_history
AI agents call signallord_get_etf_flow_history 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.
The tool appears designed to retrieve historical ETF flow information from the Signal Lord Bitcoin market intelligence system. No description is provided, but the naming pattern aligns with sibling tools (all read-only queries like 'get_btc_metrics', 'get_composite_score'). There is no indication of write, delete, execution, or financial transaction capabilities.
From the tool's definition Tool name 'signallord_get_etf_flow_history' indicates retrieval of historical ETF flow data. Suffix '_get_' and verb 'history' are consistent with querying/fetching existing data without modification.
Attacks that exploit this kind of access
signallord_get_etf_flow_history. 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_etf_flow_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 Signallord. Nothing to install.
signallord_get_etf_flow_history 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_etf_flow_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.
Set action: deny in the PolicyLayer policy for signallord_get_etf_flow_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.
signallord_get_etf_flow_history 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 →