punish_detail_get

获取计量处罚明细

SERVERTencent Ad MCP Server SOURCEandyleimc-source/tencent-ad-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/andyleimc-source-tencent-ad-mcp/punish-detail-get.md

What punish_detail_get does on Tencent Ad MCP Server

AI agents call punish_detail_get to retrieve information from Tencent Ad MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why punish_detail_get is rated Low

This tool retrieves existing punishment/penalty detail records from the Tencent Ads platform. It performs a read-only query with no modification, deletion, or execution of side effects. Fetching historical enforcement records does not create, modify, delete, or execute anything—it simply returns data.

From the tool's definition Tool name 'punish_detail_get' with description '获取计量处罚明细' (Get metering punishment details). The '_get' suffix and verb 'get/获取' indicate a retrieval operation. The 'punish_detail' refers to fetching historical punishment or penalty details/records.

Questions about punish_detail_get

What does the punish_detail_get tool do? +

获取计量处罚明细. It is categorised as a Read tool in the Tencent Ad MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on punish_detail_get? +

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

What risk level is punish_detail_get? +

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

Can I rate-limit punish_detail_get? +

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

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

punish_detail_get is provided by the Tencent Ad MCP Server MCP server (andyleimc-source/tencent-ad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Tencent Ad MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tencent Ad MCP Server's. Pull the full record:

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.