AI agents call list_features to retrieve information from MCP-Dubai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about registered features, their tool counts, and tiers—purely informational metadata about the server's capabilities. There is no mutation, deletion, execution, or financial impact. The blast radius of misuse is minimal: an agent could only learn about available tools, which is low-risk. This is a straightforward Read operation.
From the tool's definition Tool name 'list_features' and description 'List every registered MCP-Dubai feature with its tool count and tier' indicate data retrieval with no modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every registered MCP-Dubai feature with its tool count and tier. It is categorised as a Read tool in the MCP-Dubai MCP Server, which means it retrieves data without modifying state.
Register the MCP-Dubai MCP server in PolicyLayer and add a rule for list_features: 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 MCP-Dubai. Nothing to install.
list_features 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_features 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_features. 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_features is provided by the MCP-Dubai MCP server (mahdi-salmanzade/mcp-dubai). 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 →