Menambahkan kasus faraidh baru dengan data harta dan ahli waris
AI agents use tambah-kasus to create or update resources in Faraidh MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Faraidh MCP Server environment.
This tool creates new inheritance cases with financial and legal data (property and heir information). It is reversible (cases can be updated or deleted via sibling tools 'update-kasus' and 'hapus-kasus'), so it is Write rather than Destructive.
From the tool's definition Tool name 'tambah-kasus' (add case) and description 'Menambahkan kasus faraidh baru dengan data harta dan ahli waris' (adding new faraidh case with property and heir data) indicates creation of new records in a case management system.
Attacks that exploit this kind of access
Menambahkan kasus faraidh baru dengan data harta dan ahli waris. It is categorised as a Write tool in the Faraidh MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Faraidh MCP Server MCP server in PolicyLayer and add a rule for tambah-kasus: 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 Faraidh MCP Server. Nothing to install.
tambah-kasus 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 tambah-kasus 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 tambah-kasus. 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.
tambah-kasus is provided by the Faraidh MCP Server MCP server (mirzaakhena/faraidh-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 →