This record as markdown: /tools/airmang-hwpx-mcp-server/describe-template.md
What describe_template does on Hwpx
AI agents call describe_template to retrieve information from Hwpx without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why describe_template is rated Low
This tool retrieves and reports information about templates and placeholders without creating, modifying, or deleting any data. It is a query/read operation that has no side effects beyond returning structured information. Despite the broader server supporting document modification, this specific tool only reads template metadata and status.
From the tool's definition Tool name 'describe_template' and description indicating it 'returns registered template details and unfilled placeholder report' — purely descriptive operations with no modification, deletion, or execution of external processes.
Attacks that exploit this kind of access
The rule that runs describe_template safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hwpx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For describe_template, this is the rule to start with:
describe_template is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hwpx, apply this rule, and every describe_template call is checked against it from then on.
Questions about describe_template
등록 템플릿 상세와 placeholder 미충전 리포트를 반환합니다. It is categorised as a Read tool in the Hwpx MCP Server, which means it retrieves data without modifying state.
Register the Hwpx MCP server in PolicyLayer and add a rule for describe_template: 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.
describe_template 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 describe_template 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 describe_template. 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.
describe_template 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.
This server
Across the catalogue