AI agents call check_issue_status to retrieve information from Obsidian Ai Curator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries the status of an existing GitHub issue, which is a read-only operation with no side effects. It retrieves data without creating, modifying, deleting, or executing anything. The low severity reflects minimal blast radius if misused by an AI agent — it can only fetch status information.
From the tool's definition Tool name is 'check_issue_status' and description states 'Check the status of a GitHub issue' — this retrieves information about an issue without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access check_issue_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Ai Curator, and nothing reaches the server without passing your rules. This is the rule we recommend for check_issue_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_issue_status": {}
}
}check_issue_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the status of a GitHub issue. It is categorised as a Read tool in the Obsidian Ai Curator MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Ai Curator MCP server in PolicyLayer and add a rule for check_issue_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 Obsidian Ai Curator. Nothing to install.
check_issue_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 check_issue_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 check_issue_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.
check_issue_status is provided by the Obsidian Ai Curator MCP server (nwant/obsidian-ai-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Ai Curator, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 Obsidian Ai Curator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.