PodMule
by podmule.com · remote · no sign-in to list tools · v0.1.0 · published by com.podmule
Search, draft and manage your podcast workspace from your agent.
3 tools: 2 change things and 1 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things2Claude Code: ask: see these tools
- Only reads1Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http podmule https://app.podmule.com/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
3 tools
Changes things 2Claude Code: ask
ask_podmuleAsk PodMule for a concise read-only domain answer or an advisory route plan.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Ask PodMule for a concise read-only domain answer or an advisory route plan. Use this for quick questions, summaries, diagnostics, drafting, "what should I do?" prompts, and ambiguous action requests. This tool never performs writes. For exact capability contracts use search; for one selected action (read or write) use execute.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
executeExecute one OAuth-visible PodMule capability.No findings
Why it is in this group
- The name "execute" says "execute": a word for a change.
Description, as the server wrote it Execute one OAuth-visible PodMule capability. Reads run directly. Modern MCP 2026 clients with MRTR support may preview and affirm the allowlisted update_episode pilot; legacy clients and every other MCP write remain read-only. Dangerous writes are always blocked — do those in the PodMule app. Use ask_podmule for ambiguous requests and search for exact schemas.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
Only reads 1Claude Code: allow
searchSearch available PodMule capabilities for this OAuth token.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it Search available PodMule capabilities for this OAuth token. Use this when you need the exact capability name or schema before calling execute. For ambiguous domain requests, call ask_podmule first.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Oct 22, 2026, 14:38 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- none
- RFC 9728 protected resource metadata
- https://app.podmule.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://app.podmule.com/api/auth
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://app.podmule.com/mcp: tools/list returned 3 tools to an anonymous client, including ask_podmule (write), execute (write)
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http podmule https://app.podmule.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__podmule__search"
],
"ask": [
"mcp__podmule__ask_podmule",
"mcp__podmule__execute"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as podmule. Review it before you use it.