查看博客项目当前的 Git 状态（未提交的更改）
AI agents call git_status to retrieve information from Hexo Blog MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool purely inspects and reports on the state of Git uncommitted changes. It performs no write, execute, or destructive operations. This is consistent with Read category tools that retrieve or query data with no side effects. The low severity reflects minimal blast radius if misused — an AI agent calling this repeatedly would only generate diagnostic output, not cause harm.
From the tool's definition Tool name 'git_status' and description '查看博客项目当前的 Git 状态（未提交的更改）' (View the current Git status of the blog project with uncommitted changes) — this is a query/inspection operation that retrieves Git repository state without modifying, deleting, or executing…
Attacks that exploit this kind of access
查看博客项目当前的 Git 状态（未提交的更改）. It is categorised as a Read tool in the Hexo Blog MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hexo Blog MCP Server MCP server in PolicyLayer and add a rule for git_status: 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 Hexo Blog MCP Server. Nothing to install.
git_status 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 git_status 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 git_status. 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.
git_status is provided by the Hexo Blog MCP Server MCP server (leejersey/hexo-mcp-server). 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 →