get_plugin_data

Query and format data from a specific plugin

Server Sage MCP Server waggle-sensor/sage-mcp
Category Read
Risk class Low
Parameters 00 required

What get_plugin_data does on Sage MCP Server

AI agents call get_plugin_data to retrieve information from Sage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_plugin_data needs a policy

The tool queries and retrieves data from a plugin without modifying, deleting, or executing arbitrary code. It performs a read-only operation on existing plugin data, consistent with the 'Read' category for tools that retrieve or query data with no side effects. The low severity reflects the limited blast radius of querying plugin data.

From the tool's definition Tool name 'get_plugin_data' combined with description 'Query and format data from a specific plugin' indicates data retrieval without side effects.

Questions about get_plugin_data

What does the get_plugin_data tool do? +

Query and format data from a specific plugin. It is categorised as a Read tool in the Sage MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_plugin_data? +

Register the Sage MCP Server MCP server in PolicyLayer and add a rule for get_plugin_data: 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 Sage MCP Server. Nothing to install.

What risk level is get_plugin_data? +

get_plugin_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_plugin_data? +

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

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

get_plugin_data is provided by the Sage MCP Server MCP server (waggle-sensor/sage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.