プロジェクトチケットの詳細を取得します
AI agents call get_project_ticket to retrieve information from hokan MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries project ticket information from the CRM system. It performs a GET/read operation that does not modify, delete, or execute any operations. The Japanese description confirms it fetches ('取得します') ticket details. No data is created, modified, or destroyed. Risk is minimal as the tool only exposes existing data that may be restricted by normal access controls.
From the tool's definition Tool name 'get_project_ticket' and description 'プロジェクトチケットの詳細を取得します' (retrieves project ticket details) indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
プロジェクトチケットの詳細を取得します. It is categorised as a Read tool in the hokan MCP Server MCP Server, which means it retrieves data without modifying state.
Register the hokan MCP Server MCP server in PolicyLayer and add a rule for get_project_ticket: 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 hokan MCP Server. Nothing to install.
get_project_ticket 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 get_project_ticket 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 get_project_ticket. 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.
get_project_ticket is provided by the hokan MCP Server MCP server (shinonft/hokan-mcp). 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 →