get_project_affiliate_public
AI agents call get_project_affiliate_public 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 a strong indicator of a retrieval operation with no side effects. The '_public' suffix suggests this retrieves publicly-visible affiliate data. Sibling tools on the same server include other read operations (check_event_status, get_affiliate_portal_stats) and destructive/financial operations (approve_payouts, delete_incentive, delete_trigger), making the classification of this tool as a read…
From the tool's definition Tool name includes 'get_' prefix and 'public' suffix, indicating data retrieval of publicly-accessible affiliate information.
Attacks that exploit this kind of access
get_project_affiliate_public. 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_project_affiliate_public: 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_project_affiliate_public 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_project_affiliate_public 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_project_affiliate_public. 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_project_affiliate_public 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 →