Henter objekter fra et Tracelink modul. Tilgængelige moduler: ${module_names.join(
AI agents call list_objects to retrieve information from Tracelink 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 lists data from a module without modifying, deleting, or executing operations. It is a standard Read operation with low blast radius—misuse would only expose data already accessible to the user's authenticated session, not cause data loss or financial impact.
From the tool's definition Tool name 'list_objects' combined with description stating it 'Henter objekter fra et Tracelink modul' (retrieves objects from a Tracelink module). The verb 'Henter' (retrieves/fetches) indicates a query operation with no side effects.
Attacks that exploit this kind of access
Henter objekter fra et Tracelink modul. Tilgængelige moduler: ${module_names.join(. It is categorised as a Read tool in the Tracelink MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tracelink MCP Server MCP server in PolicyLayer and add a rule for list_objects: 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 Tracelink MCP Server. Nothing to install.
list_objects 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_objects 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_objects. 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_objects is provided by the Tracelink MCP Server MCP server (tracelink-devops/mcp-server). 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 →