get_affiliate_portal_stats
AI agents call get_affiliate_portal_stats 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 'get_' prefix is characteristic of read operations that retrieve existing data without modification. Affiliate portal statistics are informational metrics used for monitoring and analysis. The tool has no side effects and does not modify, execute, or commit resources. Low severity because data retrieval poses minimal risk even if misused—the worst outcome is information disclosure.
From the tool's definition Tool name 'get_affiliate_portal_stats' uses the verb 'get', which indicates retrieval of data. No description provided, but the name strongly suggests querying affiliate statistics for display/analytics purposes.
Attacks that exploit this kind of access
get_affiliate_portal_stats. 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 get_affiliate_portal_stats: 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.
get_affiliate_portal_stats 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 get_affiliate_portal_stats 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 get_affiliate_portal_stats. 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.
get_affiliate_portal_stats 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 →