opendata_plugins_create

Autonomously create a new plugin for this meta-data-mcp server

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/opendata-plugins-create.md

What opendata_plugins_create does on Meta Data Mcp

AI agents invoke opendata_plugins_create to trigger actions in Meta Data Mcp. 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.

Why opendata_plugins_create is rated High

Creating a new plugin on a live MCP server is an Execute/Write hybrid, but the most severe risk is that it introduces arbitrary new code into the server environment. An AI agent misusing this could install malicious or unintended plugins that alter server behavior, expand attack surface, or enable further exploitation. The word 'autonomously' amplifies the risk.

From the tool's definition 'Autonomously create a new plugin for this meta-data-mcp server' — this modifies the running server by installing new executable code/plugins

Questions about opendata_plugins_create

What does the opendata_plugins_create tool do? +

Autonomously create a new plugin for this meta-data-mcp server. It is categorised as a Execute tool in the Meta Data Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on opendata_plugins_create? +

Register the Meta Data MCP server in PolicyLayer and add a rule for opendata_plugins_create: 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 Meta Data Mcp. Nothing to install.

What risk level is opendata_plugins_create? +

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

Can I rate-limit opendata_plugins_create? +

Yes. Add a rate_limit block to the opendata_plugins_create 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 opendata_plugins_create completely? +

Set action: deny in the PolicyLayer policy for opendata_plugins_create. 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 opendata_plugins_create? +

opendata_plugins_create is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Meta Data, 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 Meta Data'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.