Run a tweet through all 18 quality/safety filters from the X algorithm. Returns pass/fail for each filter with explanations.
AI agents call check_filters 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 analyzes tweet quality against X's safety filters but does not execute code, modify data, delete content, or commit financial transactions. It is purely informational, retrieving filter evaluation results. The analysis is deterministic based on the tweet content provided, not on external effects. Therefore, it is classified as Read, with low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool 'check_filters' runs a tweet through filters and 'returns pass/fail for each filter with explanations' — a read-only analysis operation with no data modification, deletion, code execution, or financial impact.
Attacks that exploit this kind of access
Run a tweet through all 18 quality/safety filters from the X algorithm. Returns pass/fail for each filter with explanations. 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 check_filters: 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.
check_filters 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 check_filters 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 check_filters. 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.
check_filters 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 →