New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

build_meeting_nameplates

참석자 명단을 회의 명패 table block과 document_plan으로 변환합니다.

SERVERHwpx SOURCEairmang/hwpx-mcp-server
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/airmang-hwpx-mcp-server/build-meeting-nameplates.md

What build_meeting_nameplates does on Hwpx

AI agents use build_meeting_nameplates to create or update resources in Hwpx, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hwpx environment.

Why build_meeting_nameplates is rated Medium

The tool generates table blocks and a document plan from an attendee list, which is a write/create operation within an HWPX document. No execution, deletion, or financial action is implied. Severity is low since it only structures meeting nameplate data into document content.

From the tool's definition 'document_plan으로 변환합니다' — converts attendee list into meeting nameplate table blocks and a document plan, implying creation/modification of document content

Questions about build_meeting_nameplates

What does the build_meeting_nameplates tool do? +

참석자 명단을 회의 명패 table block과 document_plan으로 변환합니다. It is categorised as a Write tool in the Hwpx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on build_meeting_nameplates? +

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

What risk level is build_meeting_nameplates? +

build_meeting_nameplates is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit build_meeting_nameplates? +

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

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

build_meeting_nameplates is provided by the Hwpx MCP server (airmang/hwpx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Hwpx, and thousands of servers like it.

Across the catalogue

// 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 Hwpx'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.