describe_processor

Get comprehensive information about a processor.

Server Yamcs MCP Server paulmramirez/yamcs-mcp-server
Category Read
Risk class Low
Parameters 00 required

What describe_processor does on Yamcs MCP Server

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

Why describe_processor needs a policy

The tool retrieves and queries data about a processor in a Yamcs mission control system. The verb 'describe' and 'get information' are characteristic of read-only operations that do not modify, delete, or execute any actions. There is no indication of data mutation, deletion, or external operation triggering.

From the tool's definition Tool name 'describe_processor' and description 'Get comprehensive information about a processor' indicate a retrieval operation with no side effects.

Questions about describe_processor

What does the describe_processor tool do? +

Get comprehensive information about a processor. It is categorised as a Read tool in the Yamcs MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on describe_processor? +

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

What risk level is describe_processor? +

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

Can I rate-limit describe_processor? +

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

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

describe_processor is provided by the Yamcs MCP Server MCP server (paulmramirez/yamcs-mcp-server). 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.