AI agents invoke transcode to trigger actions in Sensory. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a conversion/transcoding process between sensory encoding formats. It is not a simple read (no data retrieval), not a write to persistent storage, and not destructive or financial. It actively runs a transformation operation whose output depends on the input arguments and target encoding, placing it in the Execute category.
From the tool's definition "Convert between different sensory encodings" — the tool performs a transformation/conversion operation across multiple encoding formats (SSTV, Morse, Braille, etc.)
Attacks that exploit this kind of access
Convert between different sensory encodings. It is categorised as a Execute tool in the Sensory MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sensory MCP server in PolicyLayer and add a rule for transcode: 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 Sensory. Nothing to install.
transcode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the transcode 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 transcode. 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.
transcode is provided by the Sensory MCP server (jaspertvdm/mcp-server-sensory). 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 →