获取 TAPD 需求或任务或迭代或测试用例的自定义字段配置
AI agents call get_entity_custom_fields to retrieve information from TAPD MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads configuration data about custom fields without creating, modifying, deleting, or executing any operations. It is a simple data retrieval operation with no side effects, fitting the Read category. Severity is low because unauthorized access to field configuration metadata poses minimal risk compared to data manipulation or execution tools on this server.
From the tool's definition Tool name is 'get_entity_custom_fields' and description indicates it retrieves ('获取' means 'get/fetch') custom field configurations for TAPD entities (requirements, tasks, iterations, test cases).
Attacks that exploit this kind of access
获取 TAPD 需求或任务或迭代或测试用例的自定义字段配置. It is categorised as a Read tool in the TAPD MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TAPD MCP Server MCP server in PolicyLayer and add a rule for get_entity_custom_fields: 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 TAPD MCP Server. Nothing to install.
get_entity_custom_fields is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_entity_custom_fields 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 get_entity_custom_fields. 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.
get_entity_custom_fields is provided by the TAPD MCP Server MCP server (ken19990709/mcp-server-for-tapd). 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 →