list_project_tiers
AI agents call list_project_tiers to retrieve information from Fuul MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name clearly indicates data retrieval ('list') of project tiers, which are likely configuration or reference data. No write, execute, or destructive capabilities are implied. Given the affiliate/analytics context, listing tiers is a query for informational purposes. The empty description reduces confidence slightly, but the naming convention and server context are clear.
From the tool's definition Tool name 'list_project_tiers' contains 'list', a classic Read operation pattern. Description is empty, but the sibling tools on this server include financial operations (approve_payouts) and destructive operations (delete_*), contextualizing this as a…
Attacks that exploit this kind of access
list_project_tiers. It is categorised as a Read tool in the Fuul MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fuul MCP Server MCP server in PolicyLayer and add a rule for list_project_tiers: 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 Fuul MCP Server. Nothing to install.
list_project_tiers 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_project_tiers 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_project_tiers. 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_project_tiers is provided by the Fuul MCP Server MCP server (kuyen-labs/mcp_server). 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 →