This record as markdown: /tools/airmang-hwpx-mcp-server/object-find-by-tag.md
What object_find_by_tag does on Hwpx
AI agents call object_find_by_tag 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 object_find_by_tag is rated Low
This is a search/query operation on document XML tags. It retrieves information about the document structure without side effects, making it a Read category tool. The low severity reflects that searching document metadata poses minimal risk even if misused by an agent. Confidence is high because the verb 'search' (검색) clearly indicates a non-destructive read operation.
From the tool's definition Tool name is "object_find_by_tag" and description states it "searches tags in document XML" (고급 means advanced; 검색합니다 means searches). The action is purely read-only—it queries/searches document structure without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
The rule that runs object_find_by_tag 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 object_find_by_tag, this is the rule to start with:
object_find_by_tag 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 object_find_by_tag call is checked against it from then on.
Questions about object_find_by_tag
[고급] 문서 XML에서 태그를 검색합니다. 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 object_find_by_tag: 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.
object_find_by_tag 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 object_find_by_tag 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 object_find_by_tag. 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.
object_find_by_tag 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