count_appeal_precedents_for_rejection_code

Aggregate signal-only summary of how disputes involving a given Taiwan NHI rejection code (e.g.

Server Opdstar Nhi tatsuju/opdstar-nhi-mcp
Category Read
Risk class Low
Parameters 00 required

What count_appeal_precedents_for_rejection_code does on Opdstar Nhi

AI agents call count_appeal_precedents_for_rejection_code to retrieve information from Opdstar Nhi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why count_appeal_precedents_for_rejection_code needs a policy

This tool queries and aggregates historical dispute statistics for a given rejection code. It retrieves data for analysis but does not create, modify, delete, or execute operations. The 'signal-only summary' language confirms it is informational only. No side effects or state changes occur. This is a straightforward data retrieval operation consistent with the 'Read' category.

From the tool's definition Tool name contains 'count' and description describes it as an 'Aggregate signal-only summary' — these are read-only operations that retrieve and summarize existing appeal precedent data without modification, deletion, or execution of arbitrary code.

Questions about count_appeal_precedents_for_rejection_code

What does the count_appeal_precedents_for_rejection_code tool do? +

Aggregate signal-only summary of how disputes involving a given Taiwan NHI rejection code (e.g. It is categorised as a Read tool in the Opdstar Nhi MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on count_appeal_precedents_for_rejection_code? +

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

What risk level is count_appeal_precedents_for_rejection_code? +

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

Can I rate-limit count_appeal_precedents_for_rejection_code? +

Yes. Add a rate_limit block to the count_appeal_precedents_for_rejection_code 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 count_appeal_precedents_for_rejection_code completely? +

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

count_appeal_precedents_for_rejection_code is provided by the Opdstar Nhi MCP server (tatsuju/opdstar-nhi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.