Get a task type with its full input schema.
AI agents call get_task_type to retrieve information from Morpheus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries information (a task type definition and its schema) with no side effects. It is purely informational and does not provision resources, execute workflows, modify state, or perform administrative changes. In the context of the Morpheus server managing cloud infrastructure, this is a safe read operation that helps users understand available task types before potentially using them.
From the tool's definition Tool name 'get_task_type' with description 'Get a task type with its full input schema' indicates retrieval of metadata about task types without modification, execution, or deletion.
Attacks that exploit this kind of access
Get a task type with its full input schema. It is categorised as a Read tool in the Morpheus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for get_task_type: 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 Morpheus MCP Server. Nothing to install.
get_task_type is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_task_type 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.
Set action: deny in the PolicyLayer policy for get_task_type. 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.
get_task_type is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →