Low Risk

get_user_invitation_info

获取当前用户的品牌与分公司权限列表。在导出新房佣金明细前,可用此工具检查用户有权访问的品牌(brand_id)和分公司(branchId),从返回结果中获取正确的brand_id和branchId用于后续导出。

Risk signalsAccepts freeform code/query input (code)

Part of the Yjzf server.

get_user_invitation_info is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE YJZF →

Free to start. No card required.

AI agents call get_user_invitation_info to retrieve information from Yjzf without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_user_invitation_info only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_user_invitation_info": {}
  }
}

See the full Yjzf policy for all 16 tools.

Get this rule live on your own Yjzf server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY YJZF →

View all 16 tools →

These attack patterns abuse exactly the kind of access get_user_invitation_info gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_user_invitation_info only ever does what you allow.

SECURE YJZF →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_user_invitation_info tool do? +

获取当前用户的品牌与分公司权限列表。在导出新房佣金明细前,可用此工具检查用户有权访问的品牌(brand_id)和分公司(branchId),从返回结果中获取正确的brand_id和branchId用于后续导出。. It is categorised as a Read tool in the Yjzf MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_user_invitation_info? +

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

What risk level is get_user_invitation_info? +

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

Can I rate-limit get_user_invitation_info? +

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

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

get_user_invitation_info is provided by the Yjzf MCP server (@yjzf/mcp-server-yjzf). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Yjzf tool call.

Deterministic rules across all 16 Yjzf tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.