getUsersMuting
Retrieve users muted by the authenticated user.
This record as markdown: /tools/xdevplatform-xmcp/getusersmuting.md
What getUsersMuting does on Xdevplatform/xmcp
AI agents call getUsersMuting to retrieve information from Xdevplatform/xmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getUsersMuting is rated Low
This tool queries and retrieves information about muted users—a read-only operation with no modifications or destructive actions. Severity is medium rather than low because it accesses user relationship/preference data that could reveal social connection patterns, though it only affects the authenticated user's own muting list.
From the tool's definition Tool name 'getUsersMuting' and description 'Retrieve users muted by the authenticated user' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs getUsersMuting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Xdevplatform/xmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getUsersMuting, this is the rule to start with:
getUsersMuting is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Xdevplatform/xmcp, apply this rule, and every getUsersMuting call is checked against it from then on.
Questions about getUsersMuting
Retrieve users muted by the authenticated user. It is categorised as a Read tool in the Xdevplatform/xmcp MCP Server, which means it retrieves data without modifying state.
Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for getUsersMuting: 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 Xdevplatform/xmcp. Nothing to install.
getUsersMuting 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 getUsersMuting 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 getUsersMuting. 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.
getUsersMuting is provided by the Xdevplatform/x MCP server (xdevplatform/xmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Xdevplatform/x, and thousands of servers like it.
This server
Across the catalogue