Create a new installment plan. Use this to understand the complex object structure required for installment-based payments.
AI agents use create_installment to create or update resources in Tunzaa MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tunzaa MCP Server environment.
The tool creates a new installment plan, which is a Write operation (creating data). While it involves financial payment structures, it appears to generate/configure payment plan objects rather than directly moving money or committing financial obligations.
From the tool's definition 'Create a new installment plan' - creates a new financial object/record for installment-based payments
Attacks that exploit this kind of access
Create a new installment plan. Use this to understand the complex object structure required for installment-based payments. It is categorised as a Write tool in the Tunzaa MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tunzaa MCP Server MCP server in PolicyLayer and add a rule for create_installment: 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 Tunzaa MCP Server. Nothing to install.
create_installment 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 create_installment 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 create_installment. 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.
create_installment is provided by the Tunzaa MCP Server MCP server (tunzaa/tunzaa_mcp). 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 →