发布回答, publish answer
AI agents use publish-answer to create or update resources in zhihu MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your zhihu MCP Server environment.
Publishing an answer is a reversible write operation that creates new data on the Zhihu platform. While answers can theoretically be deleted later, the act of publishing commits content to a public forum with potential reputational and engagement consequences.
From the tool's definition Tool name 'publish-answer' and description '发布回答, publish answer' indicate the tool creates new content (answers) on Zhihu platform. This is a write operation that modifies the platform's data by adding user-generated content.
Attacks that exploit this kind of access
发布回答, publish answer. It is categorised as a Write tool in the zhihu MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the zhihu MCP Server MCP server in PolicyLayer and add a rule for publish-answer: 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 zhihu MCP Server. Nothing to install.
publish-answer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the publish-answer 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 publish-answer. 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.
publish-answer is provided by the zhihu MCP Server MCP server (morrain/zhihumcpserver). 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 →