AI agents call get_ticket to retrieve information from Pearlog without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Ticket ID. |
Parameters from the server's own tool schema.
This tool queries and retrieves a single ticket record from the Pearlog project management system. It performs a read-only operation with no capability to create, modify, delete, or execute actions. The blast radius of misuse is minimal—an attacker could only access existing ticket information to which they may or may not be authorized, a typical Read-category risk.
From the tool's definition Tool name 'get_ticket' and description 'Get a single ticket by its ID' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
Get a single ticket by its ID. It is categorised as a Read tool in the Pearlog MCP Server, which means it retrieves data without modifying state.
get_ticket accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Pearlog MCP server in PolicyLayer and add a rule for get_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 Pearlog. Nothing to install.
get_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_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_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_ticket is provided by the Pearlog MCP server (mcp-server-pearlog). 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 →