Get usage metadata for a given tensor descriptor.
AI agents call get_usage_metadata to retrieve information from Tensorus MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries metadata—a read-only operation with no side effects. It follows the pattern of other analytics tools on the server (analytics_get_co_occurring_tags, analytics_get_complex_tensors, analytics_get_stale_tensors) which are all Read operations. The blast radius is minimal since it only returns information about existing tensors.
From the tool's definition The tool name 'get_usage_metadata' and description 'Get usage metadata for a given tensor descriptor' indicate a retrieval operation that queries metadata about tensor usage without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
Get usage metadata for a given tensor descriptor. It is categorised as a Read tool in the Tensorus MCP MCP Server, which means it retrieves data without modifying state.
Register the Tensorus MCP server in PolicyLayer and add a rule for get_usage_metadata: 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 Tensorus MCP. Nothing to install.
get_usage_metadata 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_usage_metadata 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_usage_metadata. 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_usage_metadata is provided by the Tensorus MCP server (tensorus/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 →