Menghitung pembagian warisan langsung tanpa menyimpan kasus
AI agents invoke hitung-langsung to trigger actions in Faraidh MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a calculation (Islamic inheritance distribution) on provided inputs and returns results without persisting data. It triggers a computation/processing operation rather than simply reading stored data or writing new records. Since it neither reads pre-existing stored data nor writes/modifies persistent state, Execute is the most appropriate category.
From the tool's definition 'Menghitung pembagian warisan langsung tanpa menyimpan kasus' — performs direct inheritance calculation without saving a case
Attacks that exploit this kind of access
Menghitung pembagian warisan langsung tanpa menyimpan kasus. It is categorised as a Execute tool in the Faraidh MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Faraidh MCP Server MCP server in PolicyLayer and add a rule for hitung-langsung: 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.
hitung-langsung is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hitung-langsung 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 hitung-langsung. 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.
hitung-langsung 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 →