Low Risk

get_view_detail

get_view_detail

How to control get_view_detail ↓

What get_view_detail does on MCP Feishu Project Manager

AI agents call get_view_detail to retrieve information from MCP Feishu Project Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_view_detail needs a policy

This tool retrieves detailed information about project views from Feishu. The 'get_' prefix, absence of modification/deletion language, and alignment with other read-only tools on the server (get_view_list, get_work_item_detail) all indicate a query operation. No mention of creating, modifying, deleting, or executing operations.

From the tool's definition Tool name 'get_view_detail' combined with sibling tools 'get_view_detail_by_name', 'get_view_list', and 'get_work_item_detail' all following retrieval patterns. Server description states 'retrieval of project views and work items' as core function.

Documented attack patterns abuse exactly the kind of access get_view_detail gives an agent:

How to control get_view_detail

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Feishu Project Manager, and nothing reaches the server without passing your rules. This is the rule we recommend for get_view_detail:

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

get_view_detail is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Feishu Project Manager — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_view_detail

What does the get_view_detail tool do? +

get_view_detail. It is categorised as a Read tool in the MCP Feishu Project Manager MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_view_detail? +

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

What risk level is get_view_detail? +

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

Can I rate-limit get_view_detail? +

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

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

get_view_detail is provided by the MCP Feishu Project Manager MCP server (roland0511/mcp-feishu-proj). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Feishu Project Manager tool call.

Start from MCP Feishu Project Manager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

6 MCP Feishu Project Manager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.