Get all 19 engagement signal weights from X
AI agents call get_signals to retrieve information from X Algorithm Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static or computed engagement signal weights from X's algorithm. It queries existing data to inform analysis but does not create, modify, delete, execute code, or trigger external operations. The read-only nature and absence of any destructive, financial, or execution capabilities make this a Read category tool with low severity.
From the tool's definition Tool name 'get_signals' and description 'Get all 19 engagement signal weights from X' indicate data retrieval without modification. The verb 'Get' and the action of obtaining pre-computed signal weights are read-only operations with no side effects.
Attacks that exploit this kind of access
Get all 19 engagement signal weights from X. It is categorised as a Read tool in the X Algorithm Toolkit MCP Server, which means it retrieves data without modifying state.
Register the X Algorithm Toolkit MCP server in PolicyLayer and add a rule for get_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 X Algorithm Toolkit. Nothing to install.
get_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_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_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_signals is provided by the X Algorithm Toolkit MCP server (mrchartist/x-algorithm-toolkit). 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 →