AI agents use audio_record_stop to create or update resources in AetherLink SDR MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AetherLink SDR MCP environment.
Stopping a recording finalizes and likely saves the audio file to disk. This is a write/finalization action — it modifies system state by ending the recording session and committing the recorded data. It is reversible in the sense that the file persists but the session ends. It does not delete data or execute arbitrary code, so Write is the most appropriate category.
From the tool's definition Stop current audio recording
Documented attack patterns abuse exactly the kind of access audio_record_stop gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AetherLink SDR MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for audio_record_stop:
{
"version": "1",
"default": "deny",
"tools": {
"audio_record_stop": {
"limits": [
{
"counter": "audio_record_stop_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}audio_record_stop stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Stop current audio recording. It is categorised as a Write tool in the AetherLink SDR MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AetherLink SDR MCP server in PolicyLayer and add a rule for audio_record_stop: 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 AetherLink SDR MCP. Nothing to install.
audio_record_stop is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the audio_record_stop 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 audio_record_stop. 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.
audio_record_stop is provided by the AetherLink SDR MCP server (n-erickson/aetherlink-sdr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AetherLink SDR MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 AetherLink SDR MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.