New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

parse-teams-url

Converts any Teams meeting URL format (short /meet/, full /meetup-join/, or recap ?threadId=) into a standard joinWebUrl. Use this before list-online-meetings when the user provides a recap or short URL.

SERVERMs 365 SOURCE@jo3zik/ms-365-mcp-server
High RISK CLASS
Category Execute
Parameters 11 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jo3zik-ms-365-mcp-server/parse-teams-url.md

What parse-teams-url does on Ms 365

AI agents invoke parse-teams-url to trigger actions in Ms 365. 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.

ParameterTypeRequiredDescription
url string Yes Teams meeting URL in any format

Parameters from the server's own tool schema.

Why parse-teams-url is rated High

parse-teams-url triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAccepts URL/endpoint input (url)

Questions about parse-teams-url

What does the parse-teams-url tool do? +

Converts any Teams meeting URL format (short /meet/, full /meetup-join/, or recap ?threadId=) into a standard joinWebUrl. Use this before list-online-meetings when the user provides a recap or short URL. It is categorised as a Execute tool in the Ms 365 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does parse-teams-url accept? +

parse-teams-url accepts 1 parameter: url. Required: url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on parse-teams-url? +

Register the Ms 365 MCP server in PolicyLayer and add a rule for parse-teams-url: 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 Ms 365. Nothing to install.

What risk level is parse-teams-url? +

parse-teams-url is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit parse-teams-url? +

Yes. Add a rate_limit block to the parse-teams-url 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.

How do I block parse-teams-url completely? +

Set action: deny in the PolicyLayer policy for parse-teams-url. 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.

What MCP server provides parse-teams-url? +

parse-teams-url is provided by the Ms 365 MCP server (@jo3zik/ms-365-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Ms 365, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ms 365's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.