get_linked_assets_counters

Get counters of linked assets from a given starting point.

Server InvGate Service Desk oci:ghcr.io/tracegazer/invgate-service-desk-mcp:0.2.0
Category Read
Risk class Low
Parameters 00 required

What get_linked_assets_counters does on InvGate Service Desk

AI agents call get_linked_assets_counters to retrieve information from InvGate Service Desk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_linked_assets_counters needs a policy

This tool retrieves and returns counter information about linked assets. The verb 'get' and the nature of returning 'counters' (read-only metrics) confirm this is a non-destructive query operation with no side effects. It poses minimal risk if misused by an AI agent, as it only exposes aggregated count data without the ability to modify, delete, or execute actions on assets.

From the tool's definition Tool name 'get_linked_assets_counters' and description 'Get counters of linked assets from a given starting point' indicate a retrieval/query operation that returns count data without modification.

Questions about get_linked_assets_counters

What does the get_linked_assets_counters tool do? +

Get counters of linked assets from a given starting point. It is categorised as a Read tool in the InvGate Service Desk MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_linked_assets_counters? +

Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for get_linked_assets_counters: 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 InvGate Service Desk. Nothing to install.

What risk level is get_linked_assets_counters? +

get_linked_assets_counters is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_linked_assets_counters? +

Yes. Add a rate_limit block to the get_linked_assets_counters 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.

How do I block get_linked_assets_counters completely? +

Set action: deny in the PolicyLayer policy for get_linked_assets_counters. 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.

What MCP server provides get_linked_assets_counters? +

get_linked_assets_counters is provided by the InvGate Service Desk MCP server (oci:ghcr.io/tracegazer/invgate-service-desk-mcp:0.2.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.