signallord_get_mtf_trend
AI agents call signallord_get_mtf_trend 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.
All sibling tools on this server use 'get_' or 'ask_' prefixes, which are standard for Read operations. The server's purpose is to expose financial market data and signals for analysis, not to execute trades or modify data. The 'mtf_trend' nomenclature suggests retrieval of multi-timeframe trend analysis data.
From the tool's definition Tool name contains 'get_' prefix which is a standard convention for retrieval operations. The server context is Bitcoin market intelligence with descriptors like 'exposes Signal Lord's composite gauge scoring, on-chain and macro regime signals, and market…
Attacks that exploit this kind of access
signallord_get_mtf_trend. 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_mtf_trend: 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_mtf_trend 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_mtf_trend 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_mtf_trend. 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_mtf_trend 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 →