AI agents call get_status_labels 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 |
|---|---|---|---|
projectId | number | — | Project ID. Omit to get the current project's labels. |
Parameters from the server's own tool schema.
This tool retrieves project metadata (status labels/kanban columns) for informational purposes only. It has no capability to create, modify, delete, or execute operations. The pattern of discovering valid values before mutation is a classic read-only lookup operation. Severity is low as unauthorized access to status labels poses minimal security risk.
From the tool's definition Tool name 'get_status_labels' and description 'Get the kanban column / status labels for a project' indicate a retrieval operation with no side effects. The description explicitly states it is used to 'discover' (query) valid status IDs, not modify them.
Attacks that exploit this kind of access
Get the kanban column / status labels for a project. Use this to discover valid status IDs before changing a ticket's status. It is categorised as a Read tool in the Pearlog MCP Server, which means it retrieves data without modifying state.
get_status_labels accepts 1 parameter: projectId. 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_status_labels: 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_status_labels 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_status_labels 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_status_labels. 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_status_labels 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 →