プロジェクトチケット一覧を取得します
AI agents call list_project_tickets 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/queries project ticket data from the hokan Insurance CRM system. It performs no mutations, deletions, or execution of external operations. The action is a simple read/list operation with no blast radius if misused—it would only expose existing data that the authenticated user has access to.
From the tool's definition Tool name 'list_project_tickets' and description 'プロジェクトチケット一覧を取得します' (Get a list of project tickets) indicate retrieval of data without modification or 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 list_project_tickets: 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.
list_project_tickets 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 list_project_tickets 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 list_project_tickets. 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.
list_project_tickets 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 →