get_metadata
AI agents call get_metadata to retrieve information from BigContext MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Metadata retrieval is a non-destructive query operation that accesses document properties without modifying, executing, or deleting data. Even if the metadata includes sensitive document properties, the tool itself performs no side effects. Low severity assigned because metadata access alone presents minimal risk in isolation, though confidence is slightly reduced due to empty description.
From the tool's definition Tool name 'get_metadata' indicates retrieval of metadata attributes from documents. No description provided, but 'get_' prefix and 'metadata' naming convention are consistent with read-only information retrieval operations.
Attacks that exploit this kind of access
get_metadata. It is categorised as a Read tool in the BigContext MCP MCP Server, which means it retrieves data without modifying state.
Register the BigContext MCP server in PolicyLayer and add a rule for get_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 BigContext MCP. Nothing to install.
get_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_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_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_metadata is provided by the BigContext MCP server (rixmerz/bigcontext_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 →