AI agents use PostV1InstancesPartnerFees to create or update resources in BlindPay MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BlindPay MCP Server environment.
This tool creates new financial configuration data (partner fees) which is reversible (fees can be updated or deleted via the sibling tools shown). This makes it Write rather than Financial (which would apply to actual money movement). It's not Destructive since the change is reversible via update/delete operations.
From the tool's definition Tool named 'PostV1InstancesPartnerFees' with description 'Add Partner Fee' performs a POST operation to create a new partner fee record. The POST HTTP method and 'Add' action indicate creation of new data.
Documented attack patterns abuse exactly the kind of access PostV1InstancesPartnerFees gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BlindPay MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for PostV1InstancesPartnerFees:
{
"version": "1",
"default": "deny",
"tools": {
"PostV1InstancesPartnerFees": {
"limits": [
{
"counter": "postv1instancespartnerfees_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}PostV1InstancesPartnerFees stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add Partner Fee. It is categorised as a Write tool in the BlindPay MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BlindPay MCP Server MCP server in PolicyLayer and add a rule for PostV1InstancesPartnerFees: 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 BlindPay MCP Server. Nothing to install.
PostV1InstancesPartnerFees is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the PostV1InstancesPartnerFees 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 PostV1InstancesPartnerFees. 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.
PostV1InstancesPartnerFees is provided by the BlindPay MCP Server MCP server (blindpaylabs/blindpay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BlindPay MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
81 BlindPay MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.