List custom emojis registered on this Rocket.Chat server
AI agents call list_custom_emojis to retrieve information from Rocket Cli without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of custom emoji metadata from the Rocket.Chat server. It performs a read-only operation with no side effects, no data modification, no code execution, and no destructive actions. The blast radius of misuse is minimal—an agent could only enumerate available emojis, which is informational only.
From the tool's definition Tool name 'list_custom_emojis' and description 'List custom emojis registered on this Rocket.Chat server' indicate a retrieval operation with no modification or execution of code/commands.
Attacks that exploit this kind of access
List custom emojis registered on this Rocket.Chat server. It is categorised as a Read tool in the Rocket Cli MCP Server, which means it retrieves data without modifying state.
Register the Rocket Cli MCP server in PolicyLayer and add a rule for list_custom_emojis: 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 Rocket Cli. Nothing to install.
list_custom_emojis 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 list_custom_emojis 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 list_custom_emojis. 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.
list_custom_emojis is provided by the Rocket Cli MCP server (jeanfbrito/rocket-cli). 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 →