get_media_metadata
AI agents call get_media_metadata to retrieve information from Windows Operations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the name alone, this tool retrieves metadata from media files without side effects. This is a read operation. The lack of a description lowers confidence slightly, but the naming convention strongly suggests a passive data retrieval function. Low severity due to read-only nature and limited blast radius if misused.
From the tool's definition Tool name 'get_media_metadata' indicates retrieval of metadata from media files. No description provided, but the name suggests querying/reading file properties rather than modification, deletion, or execution.
Attacks that exploit this kind of access
get_media_metadata. It is categorised as a Read tool in the Windows Operations MCP MCP Server, which means it retrieves data without modifying state.
Register the Windows Operations MCP server in PolicyLayer and add a rule for get_media_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 Windows Operations MCP. Nothing to install.
get_media_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_media_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_media_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_media_metadata is provided by the Windows Operations MCP server (sandraschi/windows-operations-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 →