aiva_get_affiliate

Get affiliate details and stats.

SERVERAIVA MCP Server SOURCE0800tim/aiva-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/0800tim-aiva-mcp/aiva-get-affiliate.md

WHAT IT DOES

What aiva_get_affiliate does on AIVA MCP Server

AI agents call aiva_get_affiliate to retrieve information from AIVA MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why aiva_get_affiliate is rated Low

This tool retrieves affiliate information and statistics without creating, modifying, deleting, or executing any actions. It is a simple data query operation with no side effects or blast radius if misused by an AI agent. The low severity reflects that reading affiliate metadata poses minimal risk compared to tools that could modify subscriptions, delete data, or execute external operations.

From the tool's definition Tool name 'aiva_get_affiliate' and description 'Get affiliate details and stats' indicate a retrieval operation with no data modification or execution of arbitrary commands. The 'get' verb and 'retrieve details' semantics are characteristic of Read operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs aiva_get_affiliate safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AIVA MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For aiva_get_affiliate, this is the rule to start with:

aiva_get_affiliate Allowed

aiva_get_affiliate is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "aiva_get_affiliate": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AIVA MCP Server, apply this rule, and every aiva_get_affiliate call is checked against it from then on.

FAQ

Questions about aiva_get_affiliate

What does the aiva_get_affiliate tool do? +

Get affiliate details and stats. It is categorised as a Read tool in the AIVA MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on aiva_get_affiliate? +

Register the AIVA MCP Server MCP server in PolicyLayer and add a rule for aiva_get_affiliate: 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 AIVA MCP Server. Nothing to install.

What risk level is aiva_get_affiliate? +

aiva_get_affiliate is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit aiva_get_affiliate? +

Yes. Add a rate_limit block to the aiva_get_affiliate 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.

How do I block aiva_get_affiliate completely? +

Set action: deny in the PolicyLayer policy for aiva_get_affiliate. 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.

What MCP server provides aiva_get_affiliate? +

aiva_get_affiliate is provided by the AIVA MCP Server MCP server (0800tim/aiva-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AIVA MCP Server, and thousands of servers like it.

This server

All 15 AIVA MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →get-chuck-categories on Jokes MCP Server →get_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →