query_username_changes
AI agents call query_username_changes to retrieve information from Twitter MCP Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve historical data about username modifications without modifying, deleting, or executing arbitrary code. No side effects are indicated. The empty description reduces confidence slightly, but the function name and server context strongly suggest a read-only query operation.
From the tool's definition Tool name 'query_username_changes' suggests querying/retrieving historical username data. Server description indicates this tool 'track[s] username changes', implying retrieval of past change records.
Attacks that exploit this kind of access
query_username_changes. It is categorised as a Read tool in the Twitter MCP Tool MCP Server, which means it retrieves data without modifying state.
Register the Twitter MCP Tool MCP server in PolicyLayer and add a rule for query_username_changes: 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 Twitter MCP Tool. Nothing to install.
query_username_changes 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 query_username_changes 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 query_username_changes. 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.
query_username_changes is provided by the Twitter MCP Tool MCP server (jalaj-pandey/twitter-mcp-tool). 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 →